Q. 21 How are benchmark and baseline tests different?
Ans: The process of running tests in sets is to capture information performance is baseline testing. This info can be used as a reference point when changes in the future are made to applications. On the other hand, benchmark tests are the process of comparing the performance of your system against industry standards giving by other organizations. You can, for example, run baseline tests on applications, analyze the collected results and modify many indexes on the database of a SQL Server before running the identical test once more using the previous same results to find out whether or not new results are the same, worse or better.
Q. 22 List out what are the common performance problem does user face?
Q. 23 List out some common performance bottlenecks?
Ans: Some common performance bottlenecks include
Q. 24 What are the common mistakes a performance tester does?
Ans: The common mistakes did in Performance Testing are
Q. 25 How do you identify which protocol to use for any application?
Ans: Previously Performance tester had to depend much on the development team to know about the protocol that application is using to interact with the server. Sometimes, it also used to be speculative.
However, LoadRunner provides a great help in form of Protocol Advisor from version 9.5 onwards. Protocol advisor detects the protocols that application uses and suggest us the possible protocols in which script can be created to simulate the real user.
Next: Interview Question #6
Previous: Interview Question #4
Ans: The process of running tests in sets is to capture information performance is baseline testing. This info can be used as a reference point when changes in the future are made to applications. On the other hand, benchmark tests are the process of comparing the performance of your system against industry standards giving by other organizations. You can, for example, run baseline tests on applications, analyze the collected results and modify many indexes on the database of a SQL Server before running the identical test once more using the previous same results to find out whether or not new results are the same, worse or better.
Q. 22 List out what are the common performance problem does user face?
- Longer loading time
- Poor response time
- Poor Scalability
- Bottlenecking (coding errors or hardware issues)
Q. 23 List out some common performance bottlenecks?
Ans: Some common performance bottlenecks include
- CPU Utilization
- Memory Utilization
- Networking Utilization
- Disk Usage
Q. 24 What are the common mistakes a performance tester does?
Ans: The common mistakes did in Performance Testing are
- Direct jump to multi-user tests
- Test results not validated
- Unknown workload details
- Too small run durations
- Lacking a long duration sustainability test
- Confusion on the definition of concurrent users
- Data not populated sufficiently
- A significant difference between test and production environment
- Network bandwidth not simulated
- Underestimating performance testing schedules
- Incorrect extrapolation of pilots
- Inappropriate base-lining of configurations
Q. 25 How do you identify which protocol to use for any application?
Ans: Previously Performance tester had to depend much on the development team to know about the protocol that application is using to interact with the server. Sometimes, it also used to be speculative.
However, LoadRunner provides a great help in form of Protocol Advisor from version 9.5 onwards. Protocol advisor detects the protocols that application uses and suggest us the possible protocols in which script can be created to simulate the real user.
Next: Interview Question #6
Previous: Interview Question #4
No comments :
Post a Comment