If you find bottleneck what is your next step?

Question Posted / guest

3 Answers
7039 Views
Symphony, I also Faced
E-Mail Answers

Answers were Sorted based on User's Feedback

If you find bottleneck what is your next step?..

Answer / 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

If you find bottleneck what is your next step?..

Answer / karne

U need to talk to u r Team manager and talk to Application
development team or Webservices Team and Database team ...
depending application ...

they are going to tune some queris and they will intemate
to u for next run ... so u need to compare the both results
and inform again ...

if the results will satisfy the Requirement u can redy to
submit the results other wise u have in same loop....

thanks
Karne

Is This Answer Correct ?

2 Yes

0 No

If you find bottleneck what is your next step?..

Answer / avilineni

If you find any bottleneck first we need to figure out whether it is related to application , environment or within a testing tool.

1. First step to check the testing tool if load generaters are generating load , no of active users are same as actual load , no errors in the script. If this is fine and no issues observed . Next go to second check

2. Check if the environment is up and running fine with no issues.
3. Next check the servers for any error logs in error logs, system output messages. If no errors are seen further drill down and follow bottom top approach to isolate the issue
4. Check Database for any errors , slow running queries , and system utilization if any suspicious is observed make a note of it.
5. Next check application server using any monitoring tool for heap memory , response times , Garbage collection and CPU. If any transaction response time seems to be high further drill down to method level to check the layer causing slowness
6. raise a issue in ticketing tool and assign to development team with all the analysis and talk to manager from Testing team and provide him the snapshot of it.

Is This Answer Correct ?

0 Yes

0 No

Post New Answer