MS Bond benchmark updated

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.

 

I recently added MS Bond to my benchmark and found some interesting numbers, which prompted a question on their repo.

Adam Sapek explained that the slow serialization speed I was seeing was down to the default buffer size being 64KB which is not suitable for the payload I was testing with.

Adjusting the buffer size to 256 bytes resulting in some pretty amazing result:

image

image

Fastest serialization & deserialization, and smallest payload.

Wow.

 

Have a look at the performance tuning guide, there’s quite a few tweaks you can do to improve performance further but it’ll depend on your payload.

3 Comments

  1. Pingback: MS Bond and Chiron benchmarked | theburningmonk.com

  2. WyattEpp   •  

    The two graphs don’t use the same scale or order, so it’s kind of hard to tell, but it looks like everything else received a decent speedup, too.

  3. Yan Cui   •  

    I ran them on different machines, which is why all the numbers are different. It’s the relative difference that is important here though (I would make that more prominent in future benchmarks).

Leave a Reply

Your email address will not be published.