Skip to main content

Why Early Performance Testing?

I am currently working on one of the highest profile projects in the company at the moment and I am really trying my best to nail early performance testing!

So I’m not from a performance testing background. Historically I have passed this phase of testing on to the official performance tester(s). By doing this I have removed all responsibility! Or have I?

What I have actually done here is miss out on an excellent learning opportunity and completely missed the importance of gathering performance stats early on in the project.

Over the last couple of weeks I have done some work to understand our projects “Performance Route to Live” along with some support from our performance consultants for guidance.

“Do you understand the performance requirements?”

Here is a draft of what I have come up with so far:


In my opinion it is important to gain an understanding of how individual services perform early on to give us an indication and enable us to plan for later stages. This can be done as early as System test or even in Integration.

I see the performance lab as my projects most important stage in the performance route to live, Not at all saying the other steps along the way are no important though.

We use a private on premise cloud in order for us to spin up new servers and tear down servers upon request so for us it’s pretty easy to create an isolated performance environment.

The benefits of having an isolated performance lab for us are:

  • Uncontended resources
  • Early indications of the effect of new functionality
  • Performance defects found much earlier
  • Much more confidence in the software
  • Able to regularly update the business expectations

What I am aiming for now is regular deployments to my performance lab so that throughout the project I can monitor the impact as we increase functionality setting realistic expectations and reducing the likelihood of severe performance defects at point of go live!


Maybe a future post will be to tell you about the outcome?!?!

Comments

  1. Very nice and interesting post. I have even framed few points about performance testing benefits. Hope you would like it - http://bit.ly/1ppqqMp

    ReplyDelete

Post a Comment

Popular posts from this blog

My Testbash Brighton 2017 Notes

This was my second Testbash... if you ever get the chance in the future these conferences are a must!
I took copious amounts of notes from the 9 talks and tried to highlight my key takeaways here... hope they make sense but please comment if you have any questions :-)
Amy Phillips - Continuous Delivery
A survival guide to joining a fast paced environment/project…
Where does testing fit within Continuous delivery:


As highlighted, basically from start to finish…
There are lots of things we can do when joining a project that is using Continuous Delivery but one of the main points from this talk was to do your research! There should be an element of "Continuous" in every aspect of the project.
·Learning the ling, what's the difference Continuous Delivery, Continuous Deployment, Continuous Integration, Continuous design, Continuous Improvements etc.? ·Understand what your role in the project is going to be ·Understand the teams values, What's going well and maybe what the team p…

The way we work shouldn’t be ‘Alien’ anymore, Should it!?!?

It’s been a good while since I have written anything (Mainly because I’m not that good a writer) but given my 16 months in the public sector I thought it was time… 
For a good number of years now the DevOps trend has given rise of buzzwords and methods aiming to speed delivery and it’s now an assumption of mine that most organisations are au fait with the term ‘Continuous Delivery’.
I was wrong…
Within the organisation that I am currently placed I believe I have a high-functioning collaborative team who work flexibly and in continuous cycle. We also involve the users which is a huge benefit to the development teams, but that’s not saying we get everything right 100% of the time! Teams must continue to learn and evolve to remain productive.
Our team work in one of several delivery groups and with this comes multiple challenges; Silos No single environment strategy lack of communicationsVaried ways of working.  And thats just to name a few, which is interesting when all delivery groups …

Leeds Testing Atelier - April 2018