4 ms·
Something like it needs to exist. JSON is stupidly inefficient for large sets of numbers. Except a framework just like grpc has been around for 25 years... but
by abraxas 7y ago
Something like it needs to exist. JSON is stupidly inefficient for large sets of numbers. Except a framework just like grpc has been around for 25 years... but shhhh, don't tell hipsters about IIOP, they are like new parents and need to discover things for themselves.
- fnord77 7y agodo you have any links to benchmarks showing json serialization inefficiency for large sets of numbers? I found this which shows json isn't too much worse than others, but it doesn't go into extreme cases https://github.com/eishay/jvm-serializers/wiki https://github.com/eishay/jvm-serializers/wiki
- abraxas 7y agoAnything that represents numeric values as text will be an order of magnitude slower to deserialize than a binary format. I don’t have a published benchmark but in my testing which is easy to replicate I’m storing an array of around 50 million uint64 values in a contiguous block of data to maximize deserialization speed. Just to get a sense of the difference I also tested using a JSON array as a more user friendly storage format and the penalty of deserializing the JSON and populating the array was around 20x in runtime cost in my use case. The platforms I tested on were C# and Java.