Binary and Json benchmarks updated

Yan Cui

I help clients go faster for less using serverless technologies.

DISCLAIMER : as always, you should bench­mark against your pay­load and use case, the bench­mark num­bers I have pro­duced here is unlikely to be rep­re­sen­ta­tive of your use cases and nei­ther is any­body else’s bench­mark numbers.

You can use the sim­ple test har­ness I cre­ated and see these exam­ple code to bench­mark against your par­tic­u­lar payload.

Binary

Only FsPickler and Json.Net was updated for this benchmark and there are no significant changes in performance in either update.

image

image

 

JSON

Quite a few of the JSON serializers had been updated since the last update :

  • fastJSON
  • FsPickler
  • Jil
  • MongoDB Driver
  • NetJSON
  • Json.Net
  • ServiceStack.Text
  • System.Text.Json

Of the updates, System.Text.Json has seen the biggest change in performance, nearly halved its deserialization time.

image

image

*protobuf-net is in this list purely as a benchmark to show how the tested JSON serializers compare to one of the fastest binary serializer in .Net.


Whenever you’re ready, here are 3 ways I can help you:

  1. Production-Ready Serverless: Join 20+ AWS Heroes & Community Builders and 1000+ other students in levelling up your serverless game.
  2. Consulting: If you want to improve feature velocity, reduce costs, and make your systems more scalable, secure, and resilient, then let’s work together and make it happen.
  3. Join my FREE Community on Skool, where you can ask for help, share your success stories and hang out with me and other like-minded people without all the negativity from social media.

 

8 thoughts on “Binary and Json benchmarks updated”

  1. theburningmonk

    Great, I’ll do another update in a week or two, give the others a chance to catch up ;-)

  2. That’s some through benchmark tests :-) I find the format hard to digest though, a lot of details and a lot to read. Not sure if you agree, but I personally prefer charts as a way to display benchmark results.

  3. Pingback: Binary and Json benchmarks updated | theburningmonk.com

Leave a Comment

Your email address will not be published. Required fields are marked *