[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.beFri Apr 27 04:08:57 PDT 2007
- Previous message: [Beowulf] scheduler policy design
- Next message: [Beowulf] scheduler policy design
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joe Landman wrote: > Wondering out loud. > > I think what we have here is a clear cut need for "fast virtualization" > (e.g. no/little performance penalty) which enables "fast" migration. > And I just spotted that KVM supports migration (http://kvm.qumranet.com/kvmwiki/Migration) and is integrated in the 2.6.21 kernel. This would allow the scheduler to schedule on the actual resources being used by an application and suspend and/or migrate a job whenever necessary. Would'nt such an approach be far more superior (in terms of throughput) and much easier to use ? 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
