DGTLMS & LMSDISPATCHER Guide

Administration

Load test results

How many learners can a DGTLMS platform handle at the same moment? The results measured on 3 October 2026 on a production server, from 10 to 1,200 simultaneous learners.

Administrator, IT department~5 minutesIntermediate

What we measured

Virtual learners log in and then follow a course just like real learners: dashboard, "My courses", opening a module, then a presence signal every 5 seconds and progress saved every 10 seconds. Their number increases in stages, from 10 to 1,200, each stage lasting several minutes.

The test was run on a single production server (8 cores), during the day, alongside the normal activity of the other platforms hosted on it. The figures refer to learners active at the same moment, not to enrolled learners: a platform usually has far more enrolled learners than users logged in simultaneously.

The results in charts

800learners in training at the same moment, with no slowdown
≈ 1,000active learners per server, before the processor saturates
0errors up to 400 simultaneous learners (64,042 requests)
0.03%of requests failed, even at 1,200 learners

Median response time

milliseconds, by number of simultaneous learners

Response time of the slowest 5%

milliseconds (95th percentile)

The stages are evenly spaced, not to scale. The amber zone, from 1,000 learners, shows that the processor is close to saturation. Hover over a chart to read the values.

Server processor

average use during each stage, all activity included
400 learners
34%
600 learners
46%
800 learners
64%
1,000 learners
78%
1,200 learners
89%

About 0.6 core per 100 active learners. Amber shade: close to saturation.

Lighter course player

processor used for 200 simultaneous learners, test environment
Before
93%
Lighter presence signal
66%
+ lighter progress saving
51%

45% less processor use, strictly identical SCORM tracking.

How to read the results

Detail by stage

Simultaneous learnersMedianSlowest 5%Requests / sProcessor
1035 ms108 ms——
5039 ms94 ms——
10039 ms80 ms——
20036 ms71 ms——
30032 ms76 ms——
40031 ms109 ms12834%
60039 ms1,300 ms (peak)19346%
80041 ms395 ms26564%
1,000161 ms652 ms31478%
1,200276 ms897 ms36089%

No errors up to 400 learners, out of 64,042 requests over two runs; a single failed request out of 27,463 at the 600 and 800 stages.

A lighter course player

During a course, more than 80% of requests come from the player: the presence signal and the saving of progress. We have made them lighter: the signal drops from 12.5 to 3.4 milliseconds, saving from 13.5 to 5.8. For 200 learners, the processor used drops from 93% to 51%, that is, 45% less. The SCORM tracking recorded is strictly identical, checked in the database on around ten cases.

These improvements are included in the next update of your platform.

What this means for your sessions

See also