POD refactor 1 | Define a way to do performance measurements
Extend the work that Bilal did, namely make locustfile that mimics our service load. Idea that comes to my mind is to create 2 types of locust clients WebClient that simulates communication between POD and FrontEnd, this one most of the time reads data at constant rate (like every second). There is up to 3-4 clients like that (rarely people would have more tabs opened) PluginClient that simulates communication between POD and Plugin. Let's say there can be up to 10 of such clients per user. They do read and writes more frequently than WebClient (figure out the number, figure out the ratio between reads and writes) Moreover locustfile should also prepare the database - fill it with the data (figure out the DB size we are happy with saying "yes it's realistic enough"). Before starting any tests. Making tests on empty database is pointless. On the other hand, for being able to compare results between runs databases should be filled in similar way across the runs.
Having such 2 types of clients create X number of locust clients, each simulating different user, find the moment where POD saturates (is not capable to handle requests at satifactionary rate - define boundaries).