Elo-MMR VS FlatBuffers

It is not. MMR is a system that is inherited from ELO in chess, you can read the full academic definition/breakdown on this paper https://github.com/EbTech/Elo-MMR/blob/master/paper/EloMMR.pdf if you are interested but in short is a series of Mathematical calculations and algorithms that create a number to represent players skill and use that number to match people of similar numbers. If there is a difference in the MMR between players then the underdog (the person with the lowest number) will increase their MMR by a large number since the system expected them to loose.

The author of said paper also published an implementation of it in Rust on his GitHub: https://github.com/EbTech/Elo-MMR

For multiplayer games the recent Elo-MMR is even better (faster, provable guarantees):

[1] https://github.com/EbTech/Elo-MMR

[2] https://arxiv.org/abs/2101.00400

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-...

Much more in the discussion of this particular issue onGitHub: flatbuffers:Reverse engineering #4258

Related but not Rust-specific: FlatBuffers, Cap'n Proto.

If json files are a concern because of space, you can always look into something like protobuffers or flatbuffers. But whatever you use, you should try to find a solution where you don't have to think about the actual serialization/deserialization of your objects, and can just concentrate on the data.

Or, as an alternative to protobuffers, there's also flatbuffers, which is lighter weight and needs less memory: https://google.github.io/flatbuffers/

As the title suggests, I am considering using Flatbuffers as a way to parse sensor data that has been stored in local datafiles. The project language is python.