There’s a really basic basic I didn’t mention

Our environment is well enough setup that we can make use of basic math to predict what we need come production hardware wise but some of that is a function of the overall side of environment we require right now. As we grow that will become more difficult to do and probably require us to focus more on “dark releases”.

“But if you’ve set-up your environment to maximise application performance for some performance work you might eliminate all of your scheduled jobs so you can focus on the KPI you are interested in. You need to remember to turn all of these back on when you are doing proper load testing, as you need to be as like live as possible.”

Another good bit of advice – automation of course is key to making that “turn off the jobs, turn on the jobs” thing work well. Oh and our perennial favourite monitoring can help too

Thanks for the feedback and the encouragement – been busy of late and taken some time to figure out what’s “safe” to blog about commercially speaking. Let’s see if I can’t push up that blog post rate….

You also need to make sure that you’ve properly recreated your production environment, if you are running the batch jobs – it sounds like you are pretty much there.

But if you’ve set-up your environment to maximise application performance for some performance work you might eliminate all of your scheduled jobs so you can focus on the KPI you are interested in. You need to remember to turn all of these back on when you are doing proper load testing, as you need to be as like live as possible.

This is another good blog entry Dan, you should post more often !

Alex