Update Wiki Stats

[pascaldekloe]

Can someone with a recent high-end CPU [Xeon or equivalent] run the benchmarks and update the wiki content?

[pascaldekloe]

Thank you @tommyettinger.

[tommyettinger]

Oh, please don't close the issue! There's some work needed still to use any newer Java version, and getting Java 9, 11, or especially 13 results would really be more informative. I don't have much idea of specific reasons why Thrift fails so hard all over; it seems to use javax.annotation and that's not present in Java 11 or 13, while building Thrift requires using a lower Java version (or not building Java support) because they still use Gradle 5.6.2 in the latest release and that doesn't work with Java 13... or with 11, for some other reason I couldn't figure out. Thrift, at least on the JVM, seems like outdated and broken software, and the most important info I need when comparing serializers starts with "does it even work?" I'm fully in favor of removing Thrift entirely from the benchmarks if doing so allows recent Java versions to be tested.

Then again, the Android Gradle Plugin doesn't even seem compatible with Gradle versions newer than 5.6.2 (so it doesn't allow using Java 13 either, last I checked). At least Thrift has company. It's also possible other serializers would block compilation with newer Java even after Thrift was removed or worked-around...

[FelixGV]

I can take a stab at updating the results, but I would probably keep things simple and do it on the currently supported Java version.

My hardware isn't exceptional, a 3 years old MBP, but I suppose it can serve. Let me know if you have any comments or concerns.

[pascaldekloe]

If MBP stands for MacBook Pro then you should get some reasonable numbers. Xeon would be better as that is what most production systems use. Yes please @ the current Java. 👍

[tommyettinger]

Nobody seems to have desktops available any more, heh. I didn't disable the processor clock variation feature ("Turbo Boost") that's on by default on most modern Intel mobile processors. That could affect the results if heat forced Turbo Boost to turn down the clock speed, or if something happened in the background.

[pascaldekloe]

@FelixGV, the project runs with recent Java versions now. Can you please update the wiki now?

[YShow]

Hello everyone, ill be running the benchmarks on a r7 3700x running linux Opensuse Tumbleweed, the scheduler will be on performance so the clock wont drop in any case, ill post results here so people can update the wiki, ill be using java 14.0.7, any requests please ask.

[YShow]

Seems dsl isnt working, im getting this error:
if i remember correctly dsl uses a proprietary json parser made in C# and i dont think it should be considered in this benchmark

com.dslplatform.json.ConfigurationException: Unable to serialize provided object. Failed to find serializer for: class data.media.MediaContent
        at com.dslplatform.json.DslJson.serialize(DslJson.java:2850)
        at serializers.dsljson.DSLJson$DSLJsonSerializer.serialize(DSLJson.java:42)
        at serializers.dsljson.DSLJson$DSLJsonSerializer.serialize(DSLJson.java:20)
        at serializers.BenchmarkBase.checkSingleItem(BenchmarkBase.java:554)
        at serializers.MediaItemBenchmark.checkCorrectness(MediaItemBenchmark.java:33)
        at serializers.BenchmarkBase.runMeasurements(BenchmarkBase.java:402)
        at serializers.BenchmarkBase.runTests(BenchmarkBase.java:281)
        at serializers.BenchmarkBase.runBenchmark(BenchmarkBase.java:76)
        at serializers.MediaItemBenchmark.runBenchmark(MediaItemBenchmark.java:15)
        at serializers.BenchmarkRunner.main(BenchmarkRunner.java:28)
com.dslplatform.json.ConfigurationException: Unable to serialize provided object. Failed to find serializer for: class data.media.MediaContent
        at com.dslplatform.json.DslJson.serialize(DslJson.java:2850)
        at serializers.dsljson.DSLJson$DSLJsonSerializer.serialize(DSLJson.java:42)
        at serializers.dsljson.DSLJson$DSLJsonSerializer.serialize(DSLJson.java:20)
        at serializers.MediaItemBenchmark$2.run(MediaItemBenchmark.java:75)
        at serializers.TestCaseRunner.run(TestCaseRunner.java:24)
        at serializers.BenchmarkBase.warmTest(BenchmarkBase.java:517)
        at serializers.BenchmarkBase.runMeasurements(BenchmarkBase.java:416)
        at serializers.BenchmarkBase.runTests(BenchmarkBase.java:281)
        at serializers.BenchmarkBase.runBenchmark(BenchmarkBase.java:76)
        at serializers.MediaItemBenchmark.runBenchmark(MediaItemBenchmark.java:15)
        at serializers.BenchmarkRunner.main(BenchmarkRunner.java:28)
ERROR: exit code 1

[YShow]

anyway every other one seems to have passed, i had to rename report.texfile to .txt so github would accept the upload so here it is. Ill try to fix the dsl problem or remove it completely.

stats.txt
report.txt

[tommyettinger]

Maybe some change recently broke the DSL-Platform serialization bench? I remember it being extremely fast, in the top 3 most of the time. I don't know if they moved to a toolchain that works with just a JVM. Thanks for running this, YShow !

[YShow]

Maybe some change recently broke the DSL-Platform serialization bench? I remember it being extremely fast, in the top 3 most of the time. I don't know if they moved to a toolchain that works with just a JVM. Thanks for running this, YShow !

Yes its one of the fastest serializers that exists but its not one of the most used, ill try to fix the error and run the bench again, ill also do some working on the code with minor fixes that may help some benchmarks

[YShow]

I have been upgrading the benchmarks to newer libs versions, should some of the old serializers be remove or should i keep them?
Seems a lot has changed in most libs, it will take some time before i can get a running version