From the Open Source Load Testing presentation http://www.slideshare.net/richardfriedman/open-source-load-testing True story, but leaving out a few company specific details.  One of my first entries into managing larger teams was a project which had 40-50 developers and the middleware needed to support thousands of transactions per second.  The system was built with the work of a great team and the expertise of one amazing project manager, but we needed to start load testing. Realize this was circa 2004, so pre-cloud.Read More →

From the Open Source Load Testing presentation http://www.slideshare.net/richardfriedman/open-source-load-testing Obligatory list of load failures Pope Visit Fail for Septa: http://www.phillymag.com/news/2015/07/20/septa-suspends-pope-pass-sales-technical-difficulties/ HealthCare.gov: too many links… here is a google search https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=HealthCare.gov+fail Your story – we have all had one. And as we start the tick up towards holiday season and soon to start the code freeze phase we are reminded work through our checklist.  In a good review post at gotgroove.com #1 on that list should be stress testing. For most, the priority ofRead More →

From the Open Source Load Testing presentation http://www.slideshare.net/richardfriedman/open-source-load-testing   If you have been through the process of build and running load tests, I am sure you have gone through all the emotions that come with it. From the fun of taking down your site or API, to the agony of not knowing where the bottleneck is, and eventually the eureka moment when you resolve the issue and run your next load test.  Here are some of my emotions.Read More →

From the Open Source Load Testing presentation http://www.slideshare.net/richardfriedman/open-source-load-testing Having run and worked with many teams on load testing, a pattern in the process of load testing emerges.  It is not complex, and if done right the act of load testing becomes transparent to the process of resolving performance issues. Define Requirements. As discussed in common sense of load testing, having requirements simplifies the complexity and allows you to stop load testing at a reasonable project point. Record or Create.Read More →

From the Open Source Load Testing presentation http://www.slideshare.net/richardfriedman/open-source-load-testing In this slide we will examine load testing where the application is a black-box.  When we run our test on that black box we are looking to expose a performance bottleneck, typically this bottleneck will emerge as either performance or throughput issues. Performance. Measuring the response time of requests or test plans.  Typically measured in ms or s, but it will be specific to your test plans. Throughput.  Measuring theRead More →

From the Open Source Load Testing presentation http://www.slideshare.net/richardfriedman/open-source-load-testing Slide #1 Common Sense of Load Testing You will notice the presentation does not start with ‘Why we need or What is load testing?”. In this day and age we have had too many public examples of sites, products, and APIs falling down because of scaling issues. Every day you can still find an article to point out – Thou Shalt Load Test. We make the assumption you are reading thisRead More →

We keep working on releases and updates based completely on user feedback, so keep it coming and hopefully we can continue to make load testing simple and affordable together. Gatling.io Update Multiple Feeder files – no longer only one file for Gatling load tests, now Gatling is supported on par with Apache JMeter. Split – Any text file can be split across multiple servers.   A 10,000 line csv file called users.csv run with 10 servers will be split evenly across 10Read More →

Richard Friedman recently gave a talk at FOSSCON2015  on Open Source Load Testing. It covered Common Sense of Load Testing What we measure with Load Testing Simple Load Testing Process Joys and pain of load testing When do we load test Scaling load tests old way Scaling load tests new way How we monitor the results Review of the Open Source Load Testing Tools such as JMeter, Gatling, The Grinder, and many others. Why integrate load testing with continuousRead More →

At times, we want to know the performance of our database queries under load.  These type of load tests would rarely be tested from locations outside your infrastructure.  Opening holes directly to a database in the open would be a poor security model. Redline13 JMeter Load Testing allows you to easily deploy JMeter load plans inside your AWS domain and hammer away with your queries.  In this load test, we started a MySQL instance creating aRead More →

We have been working hard on continual new enhancements to RedLine Load Testing. We roll these out as we develop them – a number of them free like Jenkins, Gatling and JMeter  support, and some of them reserved for our Professional version. Here is a recap of all of the features (and pointers to the documentation) we are offering for only $30 per month and UNLIMITED use: Clone Test A one click mechanism to re-run a previousRead More →