Details
-
Type:
Sub-task
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.6, 1.7, 1.8, 1.9
-
Fix Version/s: None
-
Component/s: Performance
-
Labels:None
-
Affected Branches:MOODLE_16_STABLE, MOODLE_17_STABLE, MOODLE_18_STABLE, MOODLE_19_STABLE
Description
It seems like much of the reason the people complain about how slow a Windows server runs Moodle is because people are running the XAMPP distribution with Moddle that they download from download.moodle.org
The issue is that the sql settings are so low that they would only work OK for a single user. Even a development machine with 512MB of memory would be better off with more production type settings, and then people would be able to test their system with several classes of students (or use it in production until they get enough expertise to get something more sophosticated going.
I would recommend the following. Some might have better values, but these work for us in a 550 student laptop school.
skip-locking
key_buffer = 150M
max_allowed_packet = 1M
table_cache = 200
sort_buffer_size = 2M
read_buffer_size = 1M
read_rnd_buffer_size = 512K
net_buffer_length = 2K
thread_stack = 64K
query_cache_size = 150M
Attachments
Issue Links
| This issue has been marked as being related by: | ||||
| MDL-14721 | Windows installer package needs a good review for usability |
|
|
|
Eloy:
Since I see you are updating the XAMPP for windows, may I assign this to you?
Feel free to just close it if you really want to keep the settings just for test development. But I think that even on Linux, many use XAMPP in production because of the ease of install.
With these settings that they will work with almost all development and first phase deployments, and would eliminate many of the speed complaints that people associate with Windows.
(Note that we have moved to Linux and like it better, but the XAMPP windows package got us going and through our first couple years with Moodle, and it probably would not have happened without the package).