Yang (Gabriel) Yu Mingjiang (Rex) Li Some Updates on Bottlenecks/Yardstick for Stress Testing Yang (Gabriel) Yu Mingjiang (Rex) Li

Contents Some Consideration of Stress Testing Preliminary works of Bottlenecks What Yardstick can do

Some Consideration of Stress Testing Stress testing is a kind of testing when the load placed on the system is beyond normal usage pattern The expected result is if the system/component is suitable for the raised load condition (large size of data, large number of users, etc.) robustness, availability, and error handling under a expected heavy load Load Testing Stress Testing Load Testing: Load testing is meant to test the system by constantly and steadily increasing the load on the system till the time it reaches the threshold limit. Example For example, to check the email functionality of an application, it could be flooded with 1000 users at a time. Now, 1000 users can fire the email transactions (read, send, delete, forward, reply) in many different ways. If we take one transaction per user per hour, then it would be 1000 transactions per hour. By simulating 10 transactions/user, we could load test the email server by occupying it with 10000 transactions/hour. Stress Testing: Under stress testing, various activities to overload the existing resources with excess jobs are carried out in an attempt to break the system down. Example: As an example, a word processor like Writer1.1.0 by OpenOffice.org is utilized in development of letters, presentations, spread sheets etc… Purpose of our stress testing is to load it with the excess of characters.

Preliminary Work of Bottlenecks Single user load testing System throughput (large number of data) Monitoring CPU usage, latency CPU burden (small package size) Monitoring CPU usage Multi-user load testing (planed) Concurrent users Monitoring package loss, system throughput, CPU usage and latency CPU resource allocation/isolation scheme Planned stress testing scenario Large number of concurrent users, small package sizes Monitoring package loss, throughput, CPU usage and latency

What Yardstick can do Type 1 Flow run in parallel Type 2 run Visual in Initial stress test Load Manager Run in parallel Time ends or Fail Start End Iterate Increase load Criteria Check Flow create destroy ping run in parallel t1 t30 t50 t0 t5 t10 t60 5 10 20 50 100 200 Load Manager Type 2 create destroy ping run in parallel Visual

Thank You Jan 2016

Preliminary Work of Bottlenecks RX PKT TX PKT PKT LOSS LATENCY CPU USAGE THROUGHPUT Task.iter() Bottlenecks Load Control Logic Yardstick Load Condition Restful Monitoring Results Reporting 7