If you find bottleneck what is your next step?
Answer Posted / ravi v v
In General the below process would be taken place when ever
we came acroos any bottlnecks.
1. If we find any bottleneck, we classify the output from
where/which part(component/system) is cuasing for this...
2. We will bring this issue to the respective team
3. They will ask for the proofs for the bottlnecks and you
should be having very strong supportings to show them.
4. Then they will tune the respective system and they will
deploy again.
5. We will conduct our tests again and compare the old one
and current results
6. if the current results satisfies the clients
requirements, we will report the same. if doesnt satisfy we
have repeat the above steps from 2.
| Is This Answer Correct ? | 4 Yes | 0 No |
Post New Answer View All Answers
Does caching have a negative effect on your load testing results?
What is the advantage of running vuser as a process than a thread?
Can anyone please mention what are the common errors that we can see while replaying the Vugen script and also while running the controller scneraio and How to handle them with a few examples. This will be greatly helpful.
Which function is used to end a nested transaction?
What is vuser script?
What is the modular approach of scripting?
Which components have you used in loadrunner ?
How to schedule a scenario?
What is vugen recording and scripting?
What are all the types of goals in goal-oriented scenario of load runner?
Which are online monitors and windows resource monitors
What is a difference between pacing and think time?
How load runner interacts with the application?
How to create a scenario?
What is ramp up and ramp down?