upb
Sandstorm
upb | Sandstorm | |
---|---|---|
6 | 51 | |
1,503 | 6,637 | |
0.3% | 0.2% | |
8.3 | 5.4 | |
about 1 month ago | 3 months ago | |
C | JavaScript | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
upb
-
C and C++ Prioritize Performance over Correctness
> There are undeniably power users for whom every last bit of performance translates to very large sums of money, and I don’t claim to know how to satisfy them otherwise.
That is the key, right there.
In 1970, C may have been considered a general-purpose programming langauge. Today, given the landscape of languages currently available, C and C++ have a much more niche role. They are appropriate for the "power users" described above, who need every last bit of performance, at the cost of more development effort.
When I'm working in C, I'm frequently watching the assembly language output closely, making sure that I'm getting the optimizations I expect. I frequently find missed optimization bugs in compilers. In these scenarios, undefined behavior is a tool that can actually help achieve my goal. The question I'm always asking myself is: what do I have to write in C to get the assembly language output I expect? Here is an example of such a journey: https://blog.reverberate.org/2021/04/21/musttail-efficient-i...
I created the https://github.com/protocolbuffers/upb project a long time ago. It's written in C, and over the years I have gotten it to a state where the speed and code size are pretty compelling. Both speed and code size are very important to the use cases where it is being used. It's a relatively small code base also. I think focused, performance-oriented kernels are the area where C makes the most sense.
-
Cap'n Proto 1.0
More and more languages are being built on top of the "upb" C library for protobuf (https://github.com/protocolbuffers/upb) which is designed around arenas to avoid this very problem.
Currently Ruby, PHP, and Python are backed by upb, but this list may expand in the future.
- Fast memcpy, A System Design
-
Implementing Hash Tables in C
Lua uses "chained scatter" (linked list, but links point to other entries in the same table, to maintain locality): https://github.com/lua/lua/blob/master/ltable.c
This is a good visual depiction of chained scatter: https://book.huihoo.com/data-structures-and-algorithms-with-...
Inspired by Lua, I did the same for upb (https://github.com/protocolbuffers/upb). I recently benchmarked upb's table vs SwissTable for a string-keyed table and found I was beating it in both insert and lookup (in insert upb is beating SwissTable by 2x).
-
Asahi Linux progress report, August 2021
> But yes, the serialized dict-of-arrays-of-dicts type stuff can be approached in a few ways, none of which are particularly beautiful.
For what it's worth, this sounds somewhat similar to protobuf (which also supports dicts, arrays, etc).
After spending many years trying to figure out the smallest, fastest, and simplest way to implement protobuf in https://github.com/protocolbuffers/upb, the single best improvement I found was to make the entire memory management model arena-based.
When you parse an incoming request, all the little objects (messages, arrays, maps, etc) are allocated on the arena. When you are done with it, you just free the arena.
In my experience this results in code that is both simpler and faster than trying to memory-manage all of the sub-objects independently. It also integrates nicely with existing memory-management schemes: I've been able to adapt the arena model to both Ruby (tracing GC) and PHP (refcounting) runtimes. You just have to make sure that the arena itself outlives any reference to any of the objects within.
-
Don't Use Protobuf for Telemetry
> Google's implementations, at least C++ and Java, are a bunch of bloated crap (or maybe they're very good, but for a use case that I haven't yet encountered).
As someone who has been working on protobuf-related things for >10 years, including creating a size-focused implementation (https://github.com/protocolbuffers/upb), and has been working on the protobuf team for >5 years, I have a few thoughts on this.
I think it is true that protobuf C++ could be a lot more lean than it currently is. That's why I created upb (above) to begin with. But there's also a bit more to this story.
The protobuf core runtime is split into two parts, "lite" and "full". Basically the full runtime contains reflection support, while the lite runtime omits it. The full runtime is much larger than the lite runtime. If you don't need runtime reflection for your protos, it's better to use "lite" by using "option optimize_for = LITE_RUNTIME" in your .proto file (https://developers.google.com/protocol-buffers/docs/proto#op...). That will cut out a huge amount of overhead in your binary. On the downside, you won't get functionality that requires reflection, including text format, JSON, or DebugString().
In addition to this, even the lite runtime can get "lighter" if you compile your binary to statically link the runtime and strip unused symbols with -ffunction-sections/-fdata-sections and gc-sections in the linker. Some parts of the lite runtime are only used in unusual situations, like ExtensionSet which is only used if your protos use proto2 extensions (https://developers.google.com/protocol-buffers/docs/proto#ex...). If you avoid this stuff, the lite runtime is quite light.
However, there is also the issue of the generated code size. The size of the generated code is generally quite large, even for lite. You are getting a generated parser, serializer, CopyFrom(), MergeFrom(), etc for every message you define. If your schema is of any size, this quickly adds up and can dwarf the size of the actual runtime. For this reason, C++ also supports "option optimize_for = CODE_SIZE" which does everything reflectively instead of generating code. This means you pay the fixed size hit from the full runtime, but the generated code size is much smaller. On the downside, "optimize_for = CODE_SIZE" has a severe speed penalty.
I have long had the goal of making https://github.com/protocolbuffers/upb competitive with protobuf C++ in speed while achieving much smaller code size. With the benefit of 10 years of hindsight and many wrong turns, upb is meeting and even surpassing these goals. It is an order of magnitude smaller, both in the core runtime and the generated code, and after some recent experiments it is beginning to significantly surpass it in speed also (I want to publish these results soon, but the code is on this branch: https://github.com/protocolbuffers/upb/pull/310).
upb has downsides that prevent it from being fully "user ready" yet: the API is still not 100% stable, there is no C++ API for the generated code yet (and C APIs for protobuf are relatively verbose and painful), it has a bunch of legacy APIs sitting around that I am just on the verge of being able to finally delete, and it doesn't support proto2 extensions yet. On the upside, it is 100% conformant on every other protobuf feature, it has full binary and JSON support, it supports reflection if you want it but also lets you omit it for code size savings.
I hope 2021 is a year when I'll be able to publish more about these results, and when upb will be a more viable choice for users who want a smaller protobuf implementation.
Sandstorm
-
Website Impersonating a Desktop Environment
Sandstorm really had this kind of feeling. Not that it presented as a desktop environment visually - but it offered a much more integrated “computer” of documents versus silod web site apps where you need to open each site to see the files in the app. https://sandstorm.io/
-
Ask HN: Experience using your user's Google Drive instead of a database?
RemoteStorage https://remotestorage.io/ seems to be trying to do this too
I also really like the https://sandstorm.io approach which goes a little farther beyond
-
Tech Independence
They tried, it was called sandstorm https://sandstorm.io/
-
Ask HN: WordPress vs. Django/Flask?
I did read from somewhere, that with Wordpress SEO plugins etc some website got to top of search results.
Those that did website with other tech did not get same results, and thinked how to compete or survive.
For security, I use Sandstorm https://sandstorm.io fork of WordPress that generates static websites. But that does not work with some interactive plugins.
-
Plunder and Urbit
Urbit made the choice to use a bunch of silly new words for familiar concepts, not because they were inventing something so new that there were no words to describe it, but because they wanted to fool people into thinking that's what they were doing. Actually they just spent 10 years trying to do https://sandstorm.io/, but made it 10 times harder than it needed to be by coming up with a wacky new set of programming languages with silly names for everything.
That's funny, and it is OK to make fun of it.
-
Cap'n Proto 1.0
I don't work at Cloudflare but follow their work and occasionally work on performance sensitive projects.
If I had to guess, they looked at the landscape a bit like I do and regarded Cap'n Proto, flatbuffers, SBE, etc. as being in one category apart from other data formats like Avro, protobuf, and the like.
So once you're committed to record'ish shaped (rather than columnar like Parquet) data that has an upfront parse time of zero (nominally, there could be marshalling if you transmogrify the field values on read), the list gets pretty short.
https://capnproto.org/news/2014-06-17-capnproto-flatbuffers-... goes into some of the trade-offs here.
Cap'n Proto was originally made for https://sandstorm.io/. That work (which Kenton has presumably done at Cloudflare since he's been employed there) eventually turned into Cloudflare workers.
Another consideration: https://github.com/google/flatbuffers/issues/2#issuecomment-...
- 1Sub.dev – A world where people pay for software
- Sandstorm: Open-source platform for self-hosting web apps
What are some alternatives?
idevicerestore - Restore/upgrade firmware of iOS devices
yunohost - YunoHost is an operating system aiming to simplify as much as possible the administration of a server. This repository corresponds to the core code, written mostly in Python and Bash.
Protobuf.NET - Protocol Buffers library for idiomatic .NET
NextCloudPi - 📦 Build code for NextcloudPi: Raspberry Pi, Odroid, Rock64, curl installer...
mbp-2016-linux - State of Linux on the MacBook Pro 2016 & 2017
sovereign - A set of Ansible playbooks to build and maintain your own private cloud: email, calendar, contacts, file sync, IRC bouncer, VPN, and more.
bloaty - Bloaty: a size profiler for binaries
Open and cheap DIY IP-KVM based on Raspberry Pi - Open and inexpensive DIY IP-KVM based on Raspberry Pi
macOS-Simple-KVM - Tools to set up a quick macOS VM in QEMU, accelerated by KVM.
DietPi - Lightweight justice for your single-board computer!
Protobuf - Protocol Buffers - Google's data interchange format
Ansible-NAS - Build a full-featured home server or NAS replacement with an Ubuntu box and this playbook.