Changing to the standar Moodle theme in our production site, these are the values that I got for perdebug:
around 100 user accounts, low traffic (no more than 10/20 students loged at the same time).
Tests Firefox and being administrator (times for loging as a simple user are, roughly, very similar).
Logging to frontapage:
RAM peak: 48.7MB Included 1075 files
Contexts for which filters were loaded: 59
Filters created: 177
Pieces of content filtered: 45
Strings filtered: 0
get_string calls: 2321
strings mem cache hits: 2516 strings
disk cache hits: 209
DB reads/writes: 1288/47
From frontpage to one of our current courses (medium size course):
RAM peak: 56MB
Included 799 files
Contexts for which filters were loaded: 7
Filters created: 21
Pieces of content filtered: 21
Strings filtered: 0
get_string calls: 2305 strings
mem cache hits: 2501 strings disk
cache hits: 210 DB reads/writes: 884/24 Session: 28.9KB
We embed Vime content in our courses, whose requests to Google Analytics slow down the uploading time.
I was wondering if there is any benchmark value I can compare with ?
Likewise, I have use Ylsow, as it was suggested in Moodle.org.
This is our moodle site:
Our original grade was 'F', and it changed to 'C', when I adopted Yslow suggestions regarding 'Content Delivery Network (CDN)'
Our poorest performance is for:
http request, DOM elements, components that are not 'cookie-free', 70 static components without a 70 static components without a far-future expiration date, etc.
This is the complete report:
I thought that, perphaps, some of the elements of our customised theme (although we don't use jquery) could be related to this poor rate. I changed to 'Standard', which is the most basic theme for Moodle, but I still got a rate 'F' in the Yslow final score (the standard theme itself has
Before I install WinCache in our test serve, I would like to ask if I should take the Yslow recommendations serious or not.
Thank you very much for your advice.