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

Benchmark for dijon with other JSON parsers which parse to ASTs #350

Closed
wants to merge 1 commit into from

Conversation

plokhotnyuk
Copy link
Owner

@plokhotnyuk plokhotnyuk commented Jul 30, 2019

OpenJDK 1.8.0_222

[info] REMEMBER: The numbers below are just data. To gain reusable insights, you need to follow up on
[info] why the numbers are the way they are. Use profilers (see -prof, -lprof), design factorial
[info] experiments, perform baseline and negative tests that provide experimental control, make sure
[info] the benchmarking environment is safe on JVM/OS/HW level, ask for reviews from the domain experts.
[info] Do not assume the numbers tell you what you want them to tell.
[info] Benchmark                        Mode  Cnt      Score      Error  Units
[info] TwitterAPIReading.borerJson     thrpt    5  25494.989 ±   17.071  ops/s
[info] TwitterAPIReading.circe         thrpt    5  16286.175 ±  911.748  ops/s
[info] TwitterAPIReading.dijon         thrpt    5  31389.195 ± 2163.507  ops/s
[info] TwitterAPIReading.jacksonScala  thrpt    5  27622.726 ± 1811.152  ops/s
[info] TwitterAPIReading.playJson      thrpt    5  17466.630 ±   58.320  ops/s
[info] TwitterAPIReading.sprayJson     thrpt    5  11166.699 ±   35.290  ops/s
[info] TwitterAPIReading.uJson         thrpt    5  15179.327 ±  728.337  ops/s

OpenJDK 11.0.4

[info] REMEMBER: The numbers below are just data. To gain reusable insights, you need to follow up on
[info] why the numbers are the way they are. Use profilers (see -prof, -lprof), design factorial
[info] experiments, perform baseline and negative tests that provide experimental control, make sure
[info] the benchmarking environment is safe on JVM/OS/HW level, ask for reviews from the domain experts.
[info] Do not assume the numbers tell you what you want them to tell.
[info] Benchmark                        Mode  Cnt      Score     Error  Units
[info] TwitterAPIReading.borerJson     thrpt    5  24304.897 ±  48.755  ops/s
[info] TwitterAPIReading.circe         thrpt    5  18018.336 ±  71.921  ops/s
[info] TwitterAPIReading.dijon         thrpt    5  31545.468 ± 143.966  ops/s
[info] TwitterAPIReading.jacksonScala  thrpt    5  28403.883 ± 604.725  ops/s
[info] TwitterAPIReading.playJson      thrpt    5  17076.075 ±  53.620  ops/s
[info] TwitterAPIReading.sprayJson     thrpt    5   9590.720 ± 102.355  ops/s
[info] TwitterAPIReading.uJson         thrpt    5  17382.400 ± 133.959  ops/s

GraalVM CE 19.1.1

[info] REMEMBER: The numbers below are just data. To gain reusable insights, you need to follow up on
[info] why the numbers are the way they are. Use profilers (see -prof, -lprof), design factorial
[info] experiments, perform baseline and negative tests that provide experimental control, make sure
[info] the benchmarking environment is safe on JVM/OS/HW level, ask for reviews from the domain experts.
[info] Do not assume the numbers tell you what you want them to tell.
[info] Benchmark                        Mode  Cnt      Score      Error  Units
[info] TwitterAPIReading.borerJson     thrpt    5  26324.186 ± 1020.598  ops/s
[info] TwitterAPIReading.circe         thrpt    5  14015.640 ±  390.269  ops/s
[info] TwitterAPIReading.dijon         thrpt    5  26626.146 ±  189.150  ops/s
[info] TwitterAPIReading.jacksonScala  thrpt    5  27869.292 ±  185.188  ops/s
[info] TwitterAPIReading.playJson      thrpt    5  12962.261 ±   52.514  ops/s
[info] TwitterAPIReading.sprayJson     thrpt    5  10607.644 ±  570.923  ops/s
[info] TwitterAPIReading.uJson         thrpt    5  14339.535 ±   89.870  ops/s

GraalVM EE 19.1.1

[info] REMEMBER: The numbers below are just data. To gain reusable insights, you need to follow up on
[info] why the numbers are the way they are. Use profilers (see -prof, -lprof), design factorial
[info] experiments, perform baseline and negative tests that provide experimental control, make sure
[info] the benchmarking environment is safe on JVM/OS/HW level, ask for reviews from the domain experts.
[info] Do not assume the numbers tell you what you want them to tell.
[info] Benchmark                        Mode  Cnt      Score      Error  Units
[info] TwitterAPIReading.borerJson     thrpt    5  29870.378 ± 2895.265  ops/s
[info] TwitterAPIReading.circe         thrpt    5  15848.356 ± 1014.002  ops/s
[info] TwitterAPIReading.dijon         thrpt    5  33883.791 ±  254.373  ops/s
[info] TwitterAPIReading.jacksonScala  thrpt    5  28376.000 ±  203.844  ops/s
[info] TwitterAPIReading.playJson      thrpt    5  15824.571 ±  849.428  ops/s
[info] TwitterAPIReading.sprayJson     thrpt    5  12025.801 ±  405.178  ops/s
[info] TwitterAPIReading.uJson         thrpt    5  15779.061 ±  455.206  ops/s

@plokhotnyuk plokhotnyuk changed the title Benchmark for dijon with other JSON parsers which parse to ATSs Benchmark for dijon with other JSON parsers which parse to ASTs Jul 30, 2019
@plokhotnyuk plokhotnyuk closed this Feb 7, 2020
@plokhotnyuk plokhotnyuk deleted the ast-parsers-only branch March 14, 2020 12:51
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

Successfully merging this pull request may close these issues.

1 participant