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
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*.
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/
The text was updated successfully, but these errors were encountered: