Performance & Resource Benchmarking
  • Performance & Resource Benchmarking
    • Governed Dashboards
      • Introduction
      • E2E Infrastructure
        • Test Dashboard Details
        • Load Test Workflow
          • Test Scenario 1 – User Concurrency 5
          • Test Scenario 2 – Concurrency Limit 10
          • Test Scenario 3 – Concurrency Limit 20
          • Test Scenario 4 – Concurrency Limit 30
          • Test Scenario 5 – Concurrency Limit 40
          • Test Scenario 6 – Concurrency Limit 50
      • Summarizing the Performance Results
      • Conclusion
    • Report
      • Introduction
      • E2E Infrastructure
      • Load Test Workflow
        • Test Scenario 1 – User Concurrency 5
        • Test Scenario 2 – Concurrency Limit 10
        • Test Scenario 3 – Concurrency Limit 20
        • Test Scenario 4 – Concurrency Limit 40
      • Summarizing the Performance Results
      • Conclusion
Powered by GitBook
On this page
  • Performance Readings
  • Resource Usage in Platform
  • Conclusion

Was this helpful?

  1. Performance & Resource Benchmarking
  2. Report
  3. Load Test Workflow

Test Scenario 3 – Concurrency Limit 20

PreviousTest Scenario 2 – Concurrency Limit 10NextTest Scenario 4 – Concurrency Limit 40

Last updated 1 year ago

Was this helpful?

This test is designed like 20 virtual cloud users concurrently loading the Report for 10 minutes.

Performance Readings

The test was configured to run up to 12 minutes and 30 seconds. A total of 15022 requests were made with a max throughput of 45 Reqs./Second.

Total Reqs.

P95

Avg

Data Sent

Data Received

Total Iterations Completed

15022

3167ms

849 ms

4.26 MB

353MB

406

Resource Usage in Platform

At start

Max

Resource Usage

CPU (Core)

0.488

8.57

8.082

MEM (GiB)

7.35

9.71

2.36

Conclusion

The system can provide 20 users concurrently with a response rate of P95 3.1 Seconds, the average response time of 0.84 Seconds, and the maximum resource usage seen for this process is 8.57 Core for processing and 9.71 GiB of memory in Platform Namespace.