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. Governed Dashboards
  3. E2E Infrastructure
  4. Load Test Workflow

Test Scenario 4 – Concurrency Limit 30

PreviousTest Scenario 3 – Concurrency Limit 20NextTest Scenario 5 – Concurrency Limit 40

Last updated 2 years ago

Was this helpful?

This test is designed like 30 virtual cloud users concurrently loading the dashboard for 10 minutes. User ramp-up and ramp-down are 2 and 1 minute respectively for the test.

Performance Readings

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

Total Reqs.

P95

Avg.

Data Sent

Data Received

Total Iterations Completed

11505

4607 ms

1596 ms

12 MB

589 MB

767

Resource Usage in Platform

Resource

At Start

Max

Resource Spike Seen

CPU (Core)

0.4

10.9

10.5

MEM (GiB)

7.59

12.3

4.71

Conclusion

The system can provide 30 users concurrently with a response rate of P95 4.6 Seconds, an average response time of 1.5 Seconds, and the maximum resource usage seen for this process is 10.9 Core of processing and 12.3 GiB of memory in the platform namespace.