Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compare the performance of Java serialization vs Jackson CBOR vs Borer vs Kryo #30

Closed
PawelLipski opened this issue May 8, 2021 · 8 comments
Assignees

Comments

@PawelLipski
Copy link
Collaborator

Each of Jackson/Borer/Kryo claims to be faster than Java serialization... let's do a simple check (a few million calls of SerializationTestKit#verify?) how do they actually compare. Let's consider a few different class objects, with ADTs/Seqs/Maps involved.

@PawelLipski
Copy link
Collaborator Author

(rel: sirthias/borer#37)

@MarconZet
Copy link
Collaborator

Maybe @HubertBalcerzak should do it? Regardless of what I do, this task will remain relevant.

@PawelLipski
Copy link
Collaborator Author

Makes sense, let's discuss on a call today...

@PawelLipski
Copy link
Collaborator Author

@plokhotnyuk
Copy link

Here is a comprehensive comparison of different JSON parsers for Scala on different JVMs using different data types and real-world samples (sources).

Also the following PR has sources and results of comparison some JSON parsers for Scala with binary parsers for Scala /Java including Java serialization: dkomanov/scala-serialization#8

@PawelLipski
Copy link
Collaborator Author

Thanks @plokhotnyuk ! let us take a look...

@MarconZet
Copy link
Collaborator

@plokhotnyuk is it possible to create a link to plokhotnyuk.github.io/jsoniter-scala/ in a way, to only show specific subset of data?

@plokhotnyuk
Copy link

@MarconZet As an option you can save it locally and remove unwonted data from provided.js.

A better option would be just running only required benchmarks on your env. and then using JMH Visualizer site to plot charts or compare results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants