The Infosys Labs research blog tracks trends in technology with a focus on applied research in Information and Communication Technology (ICT)

« How long is 'healthy' response time - response time standards? | Main | Why a 'guesstimate' while identifying the workload mix may invalidate the complete performance testing findings »

Challenges during performance testing in a shared environment

Recently in one of our performance testing project, we were given a shared environment for conducting tests. During this exercise we faced multiple challenges while loading the system, measuring the outputs, successfully completing the tests and almost all the activities.

The following points highlight some of the challenges that we faced during performance testing of a web application in shared environment.
1. System performance metrics could not be measured in consistent and accurate manner due to varying external load on the system.
2. It was hard/ not possible to identify bottleneck conditions in most of the cases. Due to this, overall usefulness of the test results was coming down drastically.
E.g. highly varying system utilization was observed on DB server due to external load. Thus, it was not possible to identify the workload at which the threshold of 40% utilization of the server was being reached, due to application transactions.
3. In some cases as part of testing activities, server instances were required to be restarted. This was not possible at times as multiple applications would be deployed on the same server instance. Restarting would affect multiple activities in the environment.
4. Things are bound to go wrong while performance testing at higher user loads. There will be high probability of environment getting clogged/ failed. As the same environment was being used for other activities, performance tests were affecting these planned activities.
5. Validations of the test results were failing big time and re-execution of the tests were required quite often.
6. There might have been a major impact on effort and timelines. 

My subsequent blog will provide details on the method we formulated for overcoming these challenges, while performance testing in the shared environment. (To be continued...)



In your next post, can you please document the approach and tools you took to conduct this test?
What cloud platform?
What test platform?
what monitoring?
What server/app analysis tools?

Cloud testing and testing apps in the cloud does present new challenges as data is generated, collected and analyzed in new ways. Test approaches and tools that are built for deployment and measurement in the cloud, for the cloud, are mandatory.

I've experienced that large global IT Service shops tend to try to apply "traditional" approaches that were never designed to work in virtualized environments, much less cloud, and experience the issues you describe in this post.


In this project, we did not had an opportunity to utilize the cloud platform. The test platform was standard physical environment, where several applications were hosted and being accessed by multiple testing teams. Standard performance testing and monitoring tools were used during the exercise.

In my next post, I will cover the approach used to mitigate these problems.

Wish you a very happy new year in advance..

Hi Harish, Did you write a subsequent blog on this anytime? Can you share on what you did to overcome those challenges?

Hema, HP

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on