National Dashboard API Performance Testing Specs and Benchmark

Performance testing and benchmark
Since we have around 600 wards in Punjab, we decided to make the national dashboard service be robust enough to handle 600 requests simultaneously in a very short time (preferably midnight when the employees ingest that day’s data).
The national dashboard service Ingest API underwent extensive stress testing where the service was tested for 25 concurrent threads (users) targeting 100 requests per minute and each request payload containing 30 records (as the ingest API is a bulk API). The service passed all the tests with 0 per cent error with a throughput of 21 requests per second, 12671 total number of samples in 10 minutes which roughly equals 21 requests per second.
The stress test ran with the following configuration and reliably persisted each and every record that was ingested -
  1. 1.
    National-dashboard-ingest service -
    • Number of pods- 5
    • Number of threads for each pod- 25
    • Heap memory- 750 MB
    • Producer linger time- 1 ms
  2. 2.
    National dashboard Kafka pipeline service -
    • Number of pods- 3
    • Number of threads for each pod- 10
    • Heap memory- 512 MB
    • Producer linger time- 1 ms
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.