Binary and Json benchmarks updated

Yan Cui

I help clients go faster for less using serverless technologies.

This article is brought to you by

Don’t reinvent the patterns. Catalyst gives you consistent APIs for messaging, data, and workflow with key microservice patterns like circuit-breakers and retries for free.

Try the Catalyst beta

DISCLAIMER : as always, you should benchmark against your payload and use case, the benchmark numbers I have produced here is unlikely to be representative of your use cases and neither is anybody else’s benchmark numbers.

You can use the simple test harness I created and see these example code to benchmark against your particular payload.

 

Binary

Only FsPickler was updated for this benchmark so there are no significant changes in performance here.

image

image

 

JSON

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

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

I have retired JayRock and JsonFx from the test since both are way behind the competition and haven’t updated for a while, so I consider both to be no longer of interest.

image

image

*protobuf-net is in this list purely as a bench­mark to show how the tested JSON seri­al­iz­ers com­pare to one of the fastest binary seri­al­izer 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. This is your one-stop shop for quickly levelling up your serverless skills.
  2. I help clients launch product ideas, improve their development processes and upskill their teams. If you’d like to work together, then let’s get in touch.
  3. Join my community on Discord, ask questions, and join the discussion on all things AWS and Serverless.

1 thought on “Binary and Json benchmarks updated”

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

Leave a Comment

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