Howard Miller wrote Dienstag, 2. April 2013, 08:30
> Of course, you need to know what you are doing to tune these up to optimise the available resources and you need to monitor them very carefully as you roll out the system.
> This is with the huge caveat that you really don't know until you have run the system and obtained some data.
Can't be more true!
A customer saw the page response times getting deteriorated. By the time it reached 12 sec they managed to identify the culprit as the Infamous Information Services (IIS, sic) and cut down the response times by an order of magnitude by moving to Apache.
They are already testing Ubuntu for the future and were not so impressed. I spent one full day benchmarking and planting monitoring tools going in one full circle to pinpoint the next problem to a the writing speed on the hard disk, which turned out to be a not so hard (emulated) hard disk in Hyper-V!
Worse, I have a premonition of the next trouble, their authentication system, a complicated Active Directory "tree" thickened over the years.
Hardware and performance
Hardware for Moodle2.3 for supported 1000 concurrent users
This discussion has been locked because a year has elapsed since the last post. Please start a new discussion topic.