I have an application with several different versions of architecture. [TLDR: the goal of the application is to let university students enrol into classes for next semester. These systems always failed 20 years ago when I was in uni, and according to my research, they still always fail today.] To …

I may be a little biased on this one given I am the author of the library. But I would including PromEx as a dependency of your project and capture the BEAM, Phoenix, and Ecto metrics after running your K6 test suite with each architecture. That way you can test in a production-esque environment and…

I’m not an expert on this, but here are my thoughts. With load testing I would definitely to try to get as close to the production infrastructure as possible to get meaningful results. This includes: The amount of servers (application and DB), The CPU and RAM config of the servers, The DB config, …

[image] stefanchrobot: I’m guessing not everybody is going to sit there on minute one and try to sign up for the classes, Maybe it’s not everybody, but I’d expect exactly that to be the problem why those systems fail. [image] stefanchrobot: Maybe there’s a way to spread out the load, e.…

Thank you, yes I think I will try to deploy to production (although probably just basic config), seed realistic data, and then I want to run the tests. So I am trying to figure out how to make it as realistic as possible. [image] stefanchrobot: I’m guessing not everybody is going to sit there …

[image] josefrichter: Given the above, they unfortunately need to confirmation in semi-realtime, (worst case lets say within seconds). Because they need to act immediately and try to frantically find another course that was their “plan B”, and slots are filling super quickly. It seems like yo…

Yeah exactly. I cast the enrolment to class genserver. The genserver adds it to its state and broadcasts it, so that all liveviews can pick it up - that way you know genserver got it, coz it shows up in your liveview, but it’s completely async. And then genserver writes it to postgres in bulk, and …

Wow, what a mess. I think that letting students of later years register before the students of previous years at least gives one a chance to register to the most wanted courses. Otherwise you randomly roll the dice and might not have a chance to attend a course at all. Since you’re planning to use …

[image] stefanchrobot: allow each student to prepare a prioritised list of courses they want to attend and spin up a GenServer for each student that attempts to sign up for the courses from top to bottom of the list. That’s a neat first solution for step 2 I think! I was thinking of various w…

Load testing advice

Questions & Help Questions

LostKobrakai January 24, 2022, 3:41pm 6

It seems like you already did the important step here though, which is decoupling accepting enrollment attempts from showing a result of “you’re in or not in”.