Q. 36 How are concurrent users differing from simultaneous users?
Ans: All simultaneous users are concurrent users but vice versa is not true.
All the users in the running scenario are Concurrent users as they are using the same application at the same time but may be or may not be doing the same tasks. Simultaneous users perform the same task at the same time. Concurrent users are made Simultaneous users through rendezvous points. Rendezvous points instruct the system to wait until a certain number of Vusers arrive so that they all can do a particular task simultaneously. In JMeter, the threads are blocked by synchronizing the timer until a particular number of threads have been blocked, and then release them at once thus creating large instantaneous load. To get more information on simultaneous and concurrent users, refer the descriptive post here.
Q. 37 What is the need for Performance testing?
Ans: Performance testing is needed to verify the below:
Ans: Following are the drawbacks of manual performance testing:
Ans: Performance Bottlenecks can identify by monitoring the application against load and stress condition. To find a bottleneck situation in performance testing monitoring and profiling tools are needed. The graph and stats provided by these monitoring tools help us to determine the condition which causes increased response time of the application. The measurements of performance of the application are based on response time, throughput, hits per sec, network delay graphs, etc.
Q. 40 What is spike testing?
Ans: Spike Testing is performed to understand how would application perform when suddenly a large number of user increased. Such type of scenario is simulated by a sudden increase in the number of users at a certain point of application and then monitoring the server behaviour.
Next: Interview Question #9
Previous: Interview Question #7
Ans: All simultaneous users are concurrent users but vice versa is not true.
All the users in the running scenario are Concurrent users as they are using the same application at the same time but may be or may not be doing the same tasks. Simultaneous users perform the same task at the same time. Concurrent users are made Simultaneous users through rendezvous points. Rendezvous points instruct the system to wait until a certain number of Vusers arrive so that they all can do a particular task simultaneously. In JMeter, the threads are blocked by synchronizing the timer until a particular number of threads have been blocked, and then release them at once thus creating large instantaneous load. To get more information on simultaneous and concurrent users, refer the descriptive post here.
Q. 37 What is the need for Performance testing?
Ans: Performance testing is needed to verify the below:
a. The response time of application at the existing and expected load
b. Maximum load resisting capacity of the application in terms of users and bulk data load
c. Stability of application under expected and unexpected user load
d. Scalability and stability of the hardware resourcesQ. 38 Why do not we go for manual performance testing?
Ans: Following are the drawbacks of manual performance testing:
a. Difficult to measure the performance of the application accurately
b. Difficult to synchronize the users.
c. A number of real-time users are required to involve in Performance Testing
d. Difficult to analyze and identify the results & bottlenecks
e. Increases the infrastructure costQ. 39 How do you identify the performance bottlenecks situations?
Ans: Performance Bottlenecks can identify by monitoring the application against load and stress condition. To find a bottleneck situation in performance testing monitoring and profiling tools are needed. The graph and stats provided by these monitoring tools help us to determine the condition which causes increased response time of the application. The measurements of performance of the application are based on response time, throughput, hits per sec, network delay graphs, etc.
Q. 40 What is spike testing?
Ans: Spike Testing is performed to understand how would application perform when suddenly a large number of user increased. Such type of scenario is simulated by a sudden increase in the number of users at a certain point of application and then monitoring the server behaviour.
Next: Interview Question #9
Previous: Interview Question #7
No comments:
Post a Comment