We created a fun little tool that lets people explore the Otel data (Traces, Logs, Metrics) they send to axiom via the console in a vi-control inspired terminal ui. As a bonus we bumped the free plan to 3 datasets so everyone can take full advantage of the ax :D
It also serves as a nice showcase what kind of tools can be built with using nothing but the public APIs
28 billion data points in 50 gigabytes are not impressive for time series use. That's nearly 2 bytes per data point, many time series databases achieve 1 or less byte per data point.
Because labels or dimensions are not stored in as a value but as a row identifier in most implementations. That results in having to scan the entire row space and look at every row name and see if it matches the lookup.
Storing labels in a row based system (like SQL) allows querying by value, not column name which takes advantage of all optimizations and indexes making it a lot faster.
That said there is nothing forbidding someone to do both, DalmatinerDB, for example, uses a column-based format for metric values but a row-based format (PostgreSQL) for dimensions.
I helped to create that spreadsheet we tried to be as fair as possible and whenever possible link reproducible, verifiable benchmarks (but then again all benchmarks are lies ;).
Agreed, the FreeBSD community has been incredibly welcoming despite differences in approach of some which is super refreshing compared to the "just do it that way we've always done it like that" you encounter in other places.
Please don't quote me on this.
I think it's not a License question but they're taking a different approach. Linux binary compatibility has been around for a while now, at least longer than modern LX zones (I don't know about old Solaris lx zones).
There are some more subtle differences like the for BSD Linux emulation is a global setting and 'lx jails' are just jails w/ a Linux userland while branded zones are special kind of zones.
Overall quite good, the system is very stable and the performance is good (probably not the fastest but decent).
The only thing to criticise (to a degree) would be that if the manual isn't followed precisely during the installation you can end up with a busted setup.
For why the choice. It's a solid distributed system, the concepts it uses the same principles as FiFo (masterless setup for high availability). Being written in Erlang means it works flawlessly on SmartOS and FreeBSD plus if you already use erlang gives the advantage to be able to look at the code if needed.
The LeoFS team is very quick to respond, works extremely diligent and takes their work serious (which is a big plus).
Even on the test system which gets brutally shut down (aka plugs pulled) about once or twice a week the installation works flawlessly even after a few month of this torment.