From c350f1702e0540dda621d9dadc98f3a252ac558c Mon Sep 17 00:00:00 2001 From: angelalvaigle Date: Sun, 12 Jan 2025 09:57:59 +0100 Subject: [PATCH] Updates --- index.html | 54 ++++++++++++++++++++++++++++++++++++++++-------------- 1 file changed, 40 insertions(+), 14 deletions(-) diff --git a/index.html b/index.html index c9ceef1..c1e2be9 100644 --- a/index.html +++ b/index.html @@ -1712,31 +1712,57 @@

13.4. Load tests

This setup simulated a gradual increase from 0 to 1000 users over a period of 5 minutes. The results obtained from the tests are summarized below:

-

Response Performance -image::13_4_gatling.png["Main results"] -The results were highly satisfactory. All responses during the simulation were successful (HTTP 200), with response times consistently below 200 milliseconds. This demonstrates the system’s ability to handle load efficiently without any significant delays.

+

Response Performance

+
+
+
+Main results +
+
+
+

The results were highly satisfactory. All responses during the simulation were successful (HTTP 200), with response times consistently below 200 milliseconds. This demonstrates the system’s ability to handle load efficiently without any significant delays.

+
+
+

Active Users

+
+
+
+Active Users per Second +
+
+
+

On average, the number of active users per second during the 5-minute simulation was approximately 15. This indicates the system’s ability to maintain a steady throughput while accommodating multiple concurrent users.

-

Active Users -image::13_4_gatling_users.png["Active Users per Second"] -On average, the number of active users per second during the 5-minute simulation was approximately 15. This indicates the system’s ability to maintain a steady throughput while accommodating multiple concurrent users.

+

Requests per Second

+
+
+
+Responses per Second +
-

Requests per Second -image::13_4_gatling_responses.png["Responses per Second"] -The average number of responses processed per second during the simulation was 24. This metric reflects the application’s capacity to handle a consistent flow of requests efficiently.

+

The average number of responses processed per second during the simulation was 24. This metric reflects the application’s capacity to handle a consistent flow of requests efficiently.

-

Response Time Distribution -image::13_4_gatling_resp_distr.png["Response Time Distribution"] -The maximum response time observed throughout the test was under 200 milliseconds, further confirming the system’s stability and quick response under load.

+

Response Time Distribution

+
+
+
+Response Time Distribution +
+
+
+

The maximum response time observed throughout the test was under 200 milliseconds, further confirming the system’s stability and quick response under load.

13.5. Usability tests

-

Informal usability tests were conducted with a few friends to gather feedback on the application’s user experience. During the tests, they navigated through the main features, including registration, login, and playing the game. The feedback was generally positive, with users finding the interface intuitive and easy to use. -The main suggestion for improvement was to reduce the loading time of images fetched from Wikidata. This could be addressed by storing the images locally to enhance performance. Overall, the application met their expectations for usability.

+

Informal usability tests were conducted with a few friends to gather feedback on the application’s user experience. During the tests, they navigated through the main features, including registration, login, and playing the game. The feedback was generally positive, with users finding the interface intuitive and easy to use.

+
+
+

The main suggestion for improvement was to reduce the loading time of images fetched from Wikidata. This could be addressed by storing the images locally to enhance performance. Overall, the application met their expectations for usability.