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

Sub-optimal deserialization performance on 1 kb payloads #168

Open
fabienrenaud opened this issue Jul 25, 2016 · 0 comments
Open

Sub-optimal deserialization performance on 1 kb payloads #168

fabienrenaud opened this issue Jul 25, 2016 · 0 comments

Comments

@fabienrenaud
Copy link

fabienrenaud commented Jul 25, 2016

I recently added logansquare to my json benchmark which compares about a dozen of java json libraries using JMH: https://github.com/fabienrenaud/java-json-benchmark

This benchmark shows serialization and deserialization throughput performance of each library for 4 payload volumes: 1 kb, 10 kb, 100 kb and 1 mb.

At first, I was a bit surprised of seeing logansquare performing about just as well as jackson (I was expecting better for logansquare) but after reading the code it generates and realizing it uses jackson's stream api for all serialization/deserialization, the results made sense.

One, though, didn't. The benchmark shows a clear performance degradation of logansquare when deserializing 1 kb payloads. I would expect that value to be at parity with jackson*.

Might be worth looking into it...

Let me know if you have any questions.

PS: The benchmarks I found on LoganSquare and mine use the same type of payload from http://www.json-generator.com/

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

No branches or pull requests

1 participant