[英语]Experiences implementing efficient java thread serialization_ mobility and persistence.pdfVIP

SOFTWARE—PRACTICE AND EXPERIENCE Softw. Pract. Exper. 2000; 00:1–7 Prepared using speauth.cls [Version: 2002/09/23 v2.2] Experiences Implementing Efficient Java Thread Serialization, Mobility and Persistence S. Bouchenak, D. Hagimont, S. Krakowiak, N. De Palma, F. Boyer INRIA (French National Institute for Research in Computer Science and Control) 655, avenue de l’Europe, Montbonnot, 38334 St-Ismier Cedex, France {Sara.Bouchenak,Daniel.Hagimont,Sacha.Krakowiak,Noel.Depalma,Fabienne.Boyer}@inria.fr SUMMARY Today, mobility and persistence are important aspects of distributed computing. They have many fields of use such as load balancing, fault tolerance and dynamic reconfiguration of applications. In this context, Java provides many useful mechanisms for the mobility of code via dynamic class loading, and the mobility or persistence of data via object serialization. However, Java does not provide any mechanism for the mobility/persistence of computation (i.e., threads). We designed and implemented a new mechanism, called Java thread serialization, that is used to build thread mobility or thread persistence. Therefore, a running Java thread can, at an arbitrary state of its execution, migrate to a remote machine where it resumes its execution, or be checkpointed on disk for possible subsequent recovery. With our services, migrating a thread is simply performed by the call of our go primitive, and checkpointing/recovering a thread is performed by the call of our store and load primitives. Several projects have recently addressed the issue of Java thread serialization, e.g., Sumatra, Wasp, JavaGo, Brakes, JavaGoX, Merpati. Some of them have attempted to minimize the overhead incurred by the thread serialization mec