Yan Cui
I help clients go faster for less using serverless technologies.
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.
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:
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.
Whenever you’re ready, here are 4 ways I can help you:
- If you want a one-stop shop to help you quickly level up your serverless skills, you should check out my Production-Ready Serverless workshop. Over 20 AWS Heroes & Community Builders have passed through this workshop, plus 1000+ students from the likes of AWS, LEGO, Booking, HBO and Siemens.
- If you want to learn how to test serverless applications without all the pain and hassle, you should check out my latest course, Testing Serverless Architectures.
- If you’re a manager or founder and want to help your team move faster and build better software, then check out my consulting services.
- If you just want to hang out, talk serverless, or ask for help, then you should join my FREE Community.
Pingback: MS Bond and Chiron benchmarked | theburningmonk.com
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.
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).