Closed GoogleCodeExporter closed 9 years ago
Original comment by riccardo.murri@gmail.com
on 30 Jan 2012 at 8:41
Hi R & C,
I've already completed this issue. Some fine tuning is now needed, in
particularly:
- I use the accounting data form our SGE cluster which first started on "25
Aug 2010 10:54:54".
- In the CSV file created by distil.py the format is like this:
jobid, submit_time, duration
Thus, we have the history for all the jobs from the beginning till nowadays.
Questions:
How should a realistic simulation look like? Better:
- What should be the time period (from the CSV) taken on each iteration
of the orchestrator: 1 hour, 12h hours, 1d...1m, etc?
- What about the scheduling interval of the orchestrator?
- maxVms?
- delay?
We'll have some fun on Tuesday :)
Tyanko
Original comment by tyanko.a...@gmail.com
on 3 Feb 2012 at 3:45
| Comment #2 on issue 4 by tyanko.alexiev:
| How should a realistic simulation look like? Better:
| - What should be the time period (from the CSV) taken on each iteration
| of the orchestrator: 1 hour, 12h hours, 1d...1m, etc?
| - What about the scheduling interval of the orchestrator?
| - maxVms?
| - delay?
These should all be configurable settings. One of the purposes of the
simulator is to let us experiment and optimize the settings given a
real workload trace.
Original comment by riccardo.murri@gmail.com
on 3 Feb 2012 at 3:52
Now all these can be passed to the simulator as configurable variables.
Original comment by tyanko.a...@gmail.com
on 7 Feb 2012 at 9:07
Original issue reported on code.google.com by
riccardo.murri@gmail.com
on 30 Jan 2012 at 8:36