5 ms·
Fury is also the fastest jvm serialization framework in the https://github.com/eishay/jvm-serializers/wiki https://github.com/eishay/jvm-serializers/wiki
by chaokunyang 3y ago
Fury is also the fastest jvm serialization framework in the https://github.com/eishay/jvm-serializers/wiki https://github.com/eishay/jvm-serializers/wiki
- marginalia_nu 3y agoWeird they aren't emphasizing competitiveness with Protobuf and Avro, which is what I'd look at long before java serialization if I wanted fast object serialization.
- chaokunyang 3y agoProtobuf/Avro doesn't support polymorphism and circular references, maybe that's one of thge reason? But even compared with protobuf, fury is 3.2x faster. When comparing with avro, fury is 5.3x faster
- TeeWEE 3y agoHow can this be faster than Protobuf? Protobuf basically does a direct storage of bytestream to memory. No parsing needed because it precompiled the stubs. Theoretically it can’t be much faster. And having an IDL is an advantage imho. Clear specs and interface design.
- chaokunyang 3y agoNot exactly. Protobuf has compression for string/numbers. Fury use different compression protocol. Another thing is that Protobuf generated code are not efficient enough. Fury generated the code at runtime, which has more information about the jvm, then it can genereate more eifficient code, avoid many memory access, branchs, and do more code optimization.