1998
DOI: 10.1016/s0164-1212(97)00014-9
|View full text |Cite
|
Sign up to set email alerts
|

The RHODOS migration facility

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
10
0

Year Published

2002
2002
2012
2012

Publication Types

Select...
4
3
1

Relationship

1
7

Authors

Journals

citations
Cited by 22 publications
(10 citation statements)
references
References 21 publications
0
10
0
Order By: Relevance
“…That is, there is no load-balancing policy; the user decides which processes to migrate and when. Examples include Accent [Zayas 1987], Locus [Thiel 1991], Utopia , DEMOS/MP [Powell and Miller 1983], V [Theimer et al 1985], NEST [Agrawal and Ezzet 1987], RHODOS [De Paoli and Goscinski 1995], and MIST [Casas et al 1995].…”
Section: Related Workmentioning
confidence: 99%
“…That is, there is no load-balancing policy; the user decides which processes to migrate and when. Examples include Accent [Zayas 1987], Locus [Thiel 1991], Utopia , DEMOS/MP [Powell and Miller 1983], V [Theimer et al 1985], NEST [Agrawal and Ezzet 1987], RHODOS [De Paoli and Goscinski 1995], and MIST [Casas et al 1995].…”
Section: Related Workmentioning
confidence: 99%
“…DNS policies, combined with a simple feedback alarm mechanism from highly utilized servers, effectively avoid Web-server system overload [19] [20]. The DNS, after receiving an address request, selects the least-loaded server.…”
Section: Server-state-based Algorithmsmentioning
confidence: 99%
“…In a study carried out by DePaoli and Goscinski [49], the migration of processes was improved by using copy-on-reference mechanisms. Incorporating copy-on-reference mechanisms into the migration of checkpoints made it possible to migrate only the minimum amount of data required to run a process on a different computer, while the majority of the process' volatile data (user stack and data heap) remained on the original computer.…”
Section: Future Workmentioning
confidence: 99%