mudassiranjum1987/moss — pull request #1 by kceb1987 (2012-11-26 01:45:47+00:00)
Title: Fix and add unit tests

Hey Mudassir,

These are my up to date changes. Please pull these changes into your gitHub for working timing system.

Please note that I've integrated your lottery scheduler, fixed timing, and addeed unit tests.

We should discuss whether we should add unit tests, how to collect statistics, and any changes that we need to make and then progress forward.

If you could pull these changes, add your priority based round robin (and add an integer priority), and then send me a pull request, I could then integrate your changes into my code, and add some statistics calculation stuff.

It might also be interesting to make a UI that displays what each of the schedulers does for each of the unitTests and then we could have a discussion about why they do different things.

For the lottery scheduler we could calculate mean, standard deviation, etc. on the time it takes to run the unit tests. To get a sense for whether adequate priority was given for priority based methods, we could calculate something like "Time To Completion for processes higher than priority 3." For lottery we could calculate statistics on mean and standard deviation for the same metric.

We could then put all this data into a chart comparing priority based round robin to FIFO to the lottery scheduler. Note that FIFO currently acts like a non-priority round robin. To get it to work like a try FIFO, you need to set quantum equal to some large number so that the processes run to completion before scheduling the next one.

Thanks,

Doug