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 3 – Concurrency Limit 20

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

Last updated 2 years ago

Was this helpful?

This test is designed like 20 virtual cloud users concurrently loading the dashboard for 10 minutes. User ramp-up and ramp-down are 2 minutes 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 9060 requests were made with a max throughput of 23 Requests/Second.

Total Reqs.

P95

Avg.

Data Sent

Data Received

Total Iterations Completed

9060

4383 ms

1340 ms

9.43MB

464 MB

602

Resource Usage in Platform

Resource

At Start

Max

Resource Spike Seen

CPU (Core)

0.407

11

10.59

MEM (GiB)

7.76

11.8

4.04

Conclusion

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