Skip to content

Spike Testing

Nirav Raje edited this page Mar 10, 2022 · 2 revisions

Spike testing measures our system behavior in time of sudden change in traffic. Our application was able to cope with change and performed as anticipated with some latency added in response time.

For our widget service, we raised the thread group to a maximum of 20 threads and kept the load for 60 seconds with these parameters, this resulted in a latency rise for some time and the system was able to go back into the general state without any failures.

Below are the results of our spike testing performed for each microservice. Below results show that each microservice is spike tolerant and functions as expected when there is a surge of requests. (Testing performed via Ultimate Thread Group plugin in JMeter)

History (Registry + DB Service)

image

image

image

Landing (UI Service)

image

image

image

image

Login (Auth + User Service)

image

image

image

image

Widget (Data Service)

image

image

image

Metadata (Metadata Service)

image

image

image

Clone this wiki locally