Scaling Tutor LMS for logged-in users
Logged-in users change everything
Public pages can be served from a page cache. Students are logged in, so most of their requests run PHP and query the database. Capacity depends on how many PHP workers your host gives you, how fast each request completes and how quickly the database answers. Object caching keeps the results of repeated queries in memory, which helps logged-in traffic most.
Where Tutor LMS does its work
Quiz attempts and answers are written to their own tables when students submit. Lesson completion writes user meta. Native eCommerce writes orders, items and meta. Tutor LMS also has an email queue table and a scheduler table for deferred tasks. On busy sites these should be processed by a real server cron rather than by visitors' page views.
Load testing
We create test students and simulate realistic journeys, such as log in, open a lesson, start a quiz, submit it, against a staging copy on equivalent hosting. That shows the breaking point before your students find it. See our performance guides.
