> Are never more than 15-20 users on the platform with logging done at the same time but even that is only one person, any transaction in Moodle, how to query a discipline comes to take 8 seconds, I think that 8 seconds is a long time just to see a discipline.
8 seconds? Too long? It is a shame for a Xeon with 8 GB RAM!
Let's start from the beginning (please supply the missing information):
- Server: Intel Xeon CPU (which one exactly: dual core? quad core? Nehalem?)
- RAM: 8 GB
- OS: Windows 2003 32 bit
- Virtualization: VMware Server
- Guest
OS: Ubuntu Server 10.10 (32 bit? 64 bit?)
RAM: 1.5 GB
This is the only VM.
First question, which has been raised twice: Why these additional layers, Windows OS and VMware, if you finally make use of Linux only? Obviously all those bloat kill the performance. Why don't you install Linux native? You don't have to purge your windows for that, install dual-boot initially. Once you are convinced you can give all the hardware to Linux.
Second question, which was also raised already: Are you sure that the 32 bit Windows 2003 make use of all 8 GB? BTW, if you put install Linux natively, take a 64 bit version.
- You ran Moodle 1.9.9 without any performance problems. After upgrading to 2.0.2 it has become too slow.
Now generally, if you think a machine is too slow, first thing is to benchmark it. You haven't explained your methods either. (What is "access time" and "access speed" or an "operation done in Moodle"?) You can for example do a parallel 1.9.11 installation and run this http://moodle.org/mod/forum/discuss.php?d=57028 and compare with the results of others for comparable machines.