You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NOTE: This is just an informational issue and not actionable/not supposed to create a change
By default we use native JSON.stringify/JSON.parse for serializing events for storage. In my benchmarks with msgpack and protobuf JSON outperformed those by an order of magnitude. The events are human readable in the file (though the additional metadata added lately somewhat convolutes the readability), but filesize is bigger than with one of the other formats.
Nodejs also provides a native serialization format via v8 (https://nodejs.org/api/v8.html#v8_serialization_api), but in a benchmark test (nodejs 15.8) that also turned out an order of magnitude slower than JSON:
NOTE: This is just an informational issue and not actionable/not supposed to create a change
By default we use native JSON.stringify/JSON.parse for serializing events for storage. In my benchmarks with msgpack and protobuf JSON outperformed those by an order of magnitude. The events are human readable in the file (though the additional metadata added lately somewhat convolutes the readability), but filesize is bigger than with one of the other formats.
Nodejs also provides a native serialization format via
v8
(https://nodejs.org/api/v8.html#v8_serialization_api), but in a benchmark test (nodejs 15.8) that also turned out an order of magnitude slower than JSON:For another benchmark of multiple serialization methods:
https://github.com/Adelost/javascript-serialization-benchmark
avro seems promising, but requires a schema for the serialized documents.
The text was updated successfully, but these errors were encountered: