Since I do a fair bit of performance tests on random things that pique my interest, it’s only natural that I should make the task of carrying out these tests easier for myself, so over the weekend I put together a simple, no frills framework to do just that!
The SimpleSpeedTester project is intended to make it easier to:
- time the execution of some code
- orchestrate multiple runs of the same test
- collate the execution time of the test runs
- provide an easy way to obtain summary for the tests
What it’s not
It’s not a profiler! It doesn’t tell you which line of your code is taking what percentage of your CPU time or how much memory is used where. It’s intended for one thing and one thing only – help you speed test a specific piece of code/method over multiple runs, collate the results and work out the average for you so you don’t have to.
To get started, download the binaries here, reference the SimpleSpeedTester.dll in your project, and all you need is one line of code to schedule a test to be run multiple times and get a summary of the test runs:
And you’re done! Easy, right? ;-)
I’ve included a couple more examples here covering the most common use cases, more will be added as I add more functionalities.
So what are you waiting for? Go on, download it and play around with it, let me know what you think, any constructive suggestions are very welcomed!
I’m an AWS Serverless Hero and the author of Production-Ready Serverless. I have run production workload at scale in AWS for nearly 10 years and I have been an architect or principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. I currently work as an independent consultant focused on AWS and serverless.
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