[Beowulf] scheduler policy design
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Toon Knapen toon.knapen at fft.beWed Apr 25 00:35:03 PDT 2007
- Previous message: [Beowulf] scheduler policy design
- Next message: [Beowulf] scheduler policy design
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joe Landman wrote: > If we can assign a priority to the jobs, so that "short" jobs get a > higher priority than longer jobs, and jobs priority decreases > monotonically with run length, and we can safely checkpoint them, and > migrate them (via a virtual container) to another node, or restart them > on one node ... then we have something nice from a throughput view point. right on. This is also exactly what the scheduler in the OS is doing. This approach thus just needs to be extrapolated to a whole cluster. Does anyone know of any projects underway that are trying to accomplish exactly this ? thanks, toon
- Previous message: [Beowulf] scheduler policy design
- Next message: [Beowulf] scheduler policy design
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
