In simulation mode, the scheduler will read jobs from a trace file as if they were coming from the LoadLeveler API, and will schedule jobs in the simulated world accordingly. 5.0 Initial Experiences To assess initial experiences of the Maui Scheduler beta 1.1, a set of objectives were defined as a point of evaluation. System statistics were monitored for a four-week period before and after installation for comparison. A failure is considered to be any time where the scheduler is down or otherwise unavailable to schedule jobs on the system. The scheduler has run to date without experiencing any major failures.
Implementation is transparent to the majority of users.
Since installation, there has been little, if any, increase in Help Desk calls. A few users have experienced some confusion because they are still required to indicate a LoadLeveler class designation. This requirement allows the flexibility of reverting back to LoadLeveler for job scheduling in the event of problems with the Maui Scheduler, and will be phased out after six weeks of successful operation. Improve system utilization. The utilization numbers obtained after the installation of the Maui Scheduler are thought to be on the low side, reflecting the need to make additional adjustments to statistics collection functions.