SGE and Scyld
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.
hanzl at noel.feld.cvut.cz hanzl at noel.feld.cvut.czTue Oct 23 06:35:35 PDT 2001
- Previous message: using mpich 1.2.2.2 with ifc
- Next message: Promise SuperTrak SX6000
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> I've heard that people simply run SGE on a node, > letting Scyld to do the load balancing. Scyld does load balancing? I can imagine MOSIX doing load balancing by migration of SGE-spawned processes but not Scyld. To my knowledge, MOSIX does transparent migration (also keeping open files and network connections, they are operated through the ghost process which remains at the original node), so it could move any SGE batch job process. On the contrary, bproc/Scyld also does process migration but this migration is not transparent - it requires collaboration of the program being migrated, or at least collaboration of the environment of this program. Naive processes can be migrated at startup only and at this time you have to decide the destination node. Scyld migration was designed to get single system image (throuht this 'remote startup' and signal redirection), not to be able to move running processes with open files and network connections. (Or did I miss some new improvements?) Regards Vaclav _______________________________________________ Beowulf mailing list, Beowulf at beowulf.org To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
- Previous message: using mpich 1.2.2.2 with ifc
- Next message: Promise SuperTrak SX6000
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
