3 ms·
If you're the author of DAMPVM or are familiar with the internals, can you comment on: 1. The costs of migrating a process. How long does it typically take to
by sigil 9y ago
If you're the author of DAMPVM or are familiar with the internals, can you comment on:
1. The costs of migrating a process. How long does it typically take to an order of magnitude -- ms, secs, mins? How much state needs to be transferred?
2. Limitations. Can all processes be migrated, or are there certain types of process state that prevent migration?
3. What process state needs to be migrated, and how does that process state get enumerated?
4. Are there cases where a process is migrated, but some of its state stays behind, and the new process uses a proxy to continue to read and write it?
Been curious about past attempts at this lately, and I've found a few by digging around. For instance, Sprite OS was a BSD offshoot in the late 80s that had some form of cross-machine process migration:
https://web.stanford.edu/~ouster/cgi-bin/papers/migration-spe.pdf https://web.stanford.edu/~ouster/cgi-bin/papers/migration-sp...
- polskibus 9y agoI'm not the author, I attended class by DAMPVM author long time ago. There are some references to publications on the main page that should lead to measurements that you're interested in. look around years 2000-2005. As far as I remember it was very efficient and shined in dynamic load scheduling using process migration. Very cool at that time. It was aimed at the HPC world (PVM), there were many interesting things done in that space that we're replaced by the Beowulf attitude towards off-the-shelf components.