JMeter

Jmeter was installed locally and was used for testing the services running on Github. We tried to make our services easy to communicate and manageable to make the code efficient so that it could run well with a cluster with 1 quad master and 3 small slaves.

For a single replica, the code functioned well enough that everything was working correctly and the Jmeter was able to receive the request and show the results.

For the Logging In of an already registered user.

The Result tree is as follows

The load time, connect time, latency, size and all the other meager details are visible in the image.

The Graph is shown below.

The output of the Summary Table is as follows which summarizes the numerical details of the graph above.

As you can see from the above output the model performed well enough for a load set of up to 160 users in one go. Besides, this microservice is fairly quick.

For the Signing In of a new user, the results are as follows.

The load time, connect time, latency, size and all the other meager details are visible in the image.

The Graph is shown below.

The output of the Summary Table is as follows which summarizes the numerical details of the graph above. As you can the sign-in is able to handle a set of at least 6 users when they all try to sign in at the same time. However, the time needed for this request is more than for the login which makes sense because here you are adding it to a new database while in the above you are just looking for a match.