Hi @derlehre,
Thanks for reaching out!
There isn’t a fixed number we can give you, because it depends much more on how the server is set up than on its raw RAM and CPU. Here is what actually decides it.
- Page caching doesn’t help on the Learn page. Students are logged in there, and caching plugins skip logged-in users. So every student request reaches PHP and the database.
- After the Learn page first loads, it works like an app. Each time a student opens a lesson or quiz, or marks progress, the browser makes a small request to the Masteriyo REST API. That means “concurrent” really means “how many requests arrive in the same second”, not how many students have the page open. Students reading a lesson or watching a video put almost no load on the server.
- The real limit is usually the number of PHP workers (PHP-FPM children) your host allows, not RAM. If you have 10 workers and each request takes about 0.3 seconds, you can serve roughly 30 requests per second before requests start to queue.
A few things will help most on a server like yours:
- Ask your host how many PHP workers you have, and raise it if you can. With 5 GB of RAM you usually have room for more.
- Enable a persistent object cache such as Redis. This helps logged-in pages a lot. Please make sure Masteriyo is on the latest version first.
- Host lesson videos on YouTube, Vimeo or Bunny rather than in the Media Library, so video traffic doesn’t use your PHP workers.
- Keep the plugin count low on the Learn page, since every active plugin loads on each request.
If you want a real number for your site, a load test with a tool like k6 or Loader.io against a test copy of the site, using logged-in student accounts, will tell you exactly where it starts to slow down.
Hope this helps! Let us know if you have any other questions.
