Since I’m liking git more and more by the day, with tools such as SmartGit and GitFlow making the task of managing even a complex branching model a relatively easy task, I’ve decided to move my Simple Speed Tester project over to github!
Simple Speed Tester is a very simple framework I wrote to help me run benchmarks and is used to power my JSON and binary serializers benchmarks. It takes cares of some of the orchestration that you tend to do when running benchmarks, e.g.:
- repeating a test multiple times
- time the individual runs
- ignore the min and max runs and use the rest to calculate a meaningful average
It’s intended to be really easy to use (see examples here) and for one and only one use case – help you speed test a specific piece of code!
If you’re like me and like to run your own benchmarks then check it out, you can also install it via Nuget.
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong