From 68445666405197b5f5913be9439bf6dabd4394c9 Mon Sep 17 00:00:00 2001 From: Francesco Bottalico Date: Sat, 6 Jan 2024 12:15:17 +0100 Subject: [PATCH] Add locust report and locust section in README --- README.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/README.md b/README.md index 0cd9bd2..4c82a60 100644 --- a/README.md +++ b/README.md @@ -208,6 +208,21 @@ Here's the view to the monitors: ![Second Monitor](./docs/images/BU/monitor2.png) +## Load testing using Locust + +Lastly we tested the performances of the application using **Locust**, all the possible requests are defined in *locustfile.py*, in particular we test all the four different endpoints of our API: +- Get models list (GET request) +- Get model info (GET request) +- Get image prediction (POST request) +- Get context prediction (POST request) + +POST requests are done more frequently as they are the main functionality of our service. + +Our service is quite heavy as the model is around 100M parameters and the user has to send to the server one or more images (the predict_image endpoint is the one that has the highest response time), so our server suffers from high response times even with only a few users connected at the time. +This issue could be solved by simply upgrading the hosting service, as the one we are using is a very basic one. + +[Here](./reports/locust_report.html) you can find a short report generated by Locust. + ---