DOCSLIB.ORG

Task Management Issues in Distributed Systems Abstract 1 Introduction 2 Techniques and Attributes of Task Management

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Task Management Issues in Distributed Systems Abstract 1 Introduction 2 Techniques and Attributes of Task Management Task Management Issues in Distributed Systems Ahilan Anantha, Maki Sugimoto, Andreas Suryawan, Peter Tran University of California, San Diego November 21, 1998 Abstract tem architect: complexity, residual dep enden- cies, p erformance, and transparency. [7 ] We One of the main goals of distributed systems is analyze how each op erating system cop es with allowing idle pro cessing resources to b e utilized. these con icting factors to provide eciency To accomplish this, there must b e mechanisms and maintainability. And nally, we consider to distribute tasks across machines. We exam- improvements to these systems. ine the task management mechanisms provided by several distributed op erating systems, and 2 Techniques and Attributes analyze their e ectiveness. of Task Management 1 Intro duction 2.1 Ownership of CPU Resources A ma jor motivation for constructing a dis- The op erating systems we discuss in this pap er tributed op erating system is to p erform co or- fall into two basic classes of environments: 1 dination of decentralized resources in order to those where machines are "owned" by particu- raise the utilization of the system as a whole. lar users, such that a machine's pro cessing may It is through the management of tasks that a be used only when the owner is not using it, system is able to optimize the parallelism b eing and 2 where there is notion of ownership of ma- o ered, thereby increasing utilization. chines, all pro cessors are available for use by all There are quite a few interesting attributes users. Op erating systems of the rst class are of distributed op erating systems, and notable typically designed for environments of graphical techniques used in handling these. We examine workstations. the following attributes and techniques of task The Sprite and Condor op erating systems are management: designed for the lab graphical workstation en- vironment. There is no separate CPU server 1. Ownership of CPU resources cluster, the workstations themselves make up the distributed system. A user is exp ected to 2. Homogeneous vs heterogeneous environ- interact with the op erating system by way of ment a windowing system, which is a highly CPU 3. Remote execution/pro cess migration and memory intensive interactive pro cess. In- teractive pro cesses have randomly uctuating 4. Namespace transparency loads b ecause they act in resp onse to user activity, which itself is randomly uctuating. 5. Load information and control manager At the same time, interactive pro cesses have Design choices made in the systems surveyed minimum delay requirements b ecause users re- re ect a set of tradeo s considered by the sys- quire real-time resp onse. Windowing systems 1 nals would have minimal pro cessing resources p ose an even greater problem b ecause they re- to o er. All the resources of a graphical ter- quire a large p ercentage of pro cessing power, minal can thus be reserved for the windowing while traditional text mo de interaction is fairly system. lightweight. In order to satisfy these delay re- quirements, it b ecomes necessary to reserve the Clouds, Alpha, MOSIX, Plan 9, and Solaris maximum amount of CPU resources that a win- MC fall under this category. Solaris MC pro- dowing system would require. vides a pro cess migration mechanism for server In non-distributed systems, the user of a machines, allowing pro cesses to be migrated graphical workstation is exp ected to actively across server machines in cases where one server control which pro cesses may run on the system must be brought down for maintenance. In to satisfy his delay requirements. If the user these cases, migrated pro cesses can b e p ermit- of a graphical workstation has ownership of all ted to be inecient and to tax the resources the user pro cesses that can hog the system re- of the hosting system. But the necessity of sources, he can susp end or terminate the pro- maintaining services across server disconnec- cesses that prevent the useability of the console. tions outweighs these factors. Therefore So- However, if other users were p ermitted to eas- laris MC suggests the need for a distinction ily run pro cesses on remote systems, the console between servers which are prepared to o er user will lose the ability to control the interac- the resources to accept migrated pro cesses and tive resp onse time. user workstations which are not willing to ac- For this reason, these op erating systems give cept the burden of migrated pro cesses. Clouds, a second class status to remote pro cesses. Re- Alpha, and Plan 9 are alike in that they con- mote pro cesses are only allowed to utilize the sist of separate highend CPU and data servers. resources of a workstation if the workstation is A MOSIX system consists of a large number of not already busy serving its console user. The commo dityworkstations, all of whichmay play CPU resources can b e taken back from remote an equal part in serving data and pro cessing. pro cesses if the console user desires them. As such, the console user can be considered the 2.2 Remote Execution owner of a workstation's CPU resources. Remote execution and pro cess migration are Sprite and Condor will only p ermit remote the techniques used in distributed systems to pro cesses to run on a system when the system share CPU resources. Remote execution is the is idle and will evict remote pro cesses once a ability to create pro cesses on remote machines. user starts using the console. Pro cess migration is the ability to relo cate pro- The other class of distributed systems con- cesses b etween no des in mid-execution. sists of environments of dedicated CPU servers, Plan 9 supp orts remote execution on CPU data servers, and graphical terminals. The bulk servers explicitly sp eci ed by the user. Pro- of the pro cessing power in these environments cesses cannot be migrated, therefore remotely is contained in the CPU server. The computers executed pro cesses sp end their entire lifespan with graphical displays are essentially graphical on the remote CPU server, from creation to ter- terminals, they have sucient pro cessing abil- mination. Condor also supp orts remote execu- ityto run the windowing system pro cesses but tion only. require no more. All other CPU intensive pro- Sprite supp orts remote execution through the cesses are executed remotely on a CPU server. mechanism of pro cess migration. A request for No user "owns" the CPU server, every user remote execution of a new pro cess on Sprite gets a guaranteed share of its resources. Con- would need to be reduced to creating the pro- versely, no remote pro cesses would be allowed cess lo cally, and attempting to migrate the pro- on a graphical terminal. The work of trying cess so on after. In the case of an immediate to determine whether a graphical workstation remote execution, lo cal memory need not b e al- is idle is unnecessary, since the graphical termi- 2 is a path of execution made up of a series of lo cated for the co de and data if an idle com- calls to ob ject metho ds. Each call is referred puter is available to start with. Sprite, however, to as an invo cation that the ob ject resp onds do esn't provide this optimization. All execution to. An ob ject by itself is passive. When a b egins lo cally. thread invokes an ob ject's metho d, the thread Pro cess migration is only a request that an enters that ob ject's virtual-address space and application can make. Pro cesses are only p er- b egins execution. Eachinvo cation of a metho d mitted to execute on remote workstations that is called a segment of the thread that invokes are idle. If there are no idle machines then it. This segmentation of threads is how Clouds the request may be denied and the pro cess provides distributed execution. would continue to execute on the lo cal machine. Note how this is di erent from the tradi- Therefore, a pro cess cannot also b e exp ected to tional mo del of pro cesses and pro cess migration. b e able to b egin execution on a remote system There, a pro cess executes within one virtual- either. address space unless it is migrated to another When the computer ceases to b e idle, all re- no de. Migration is exp ensive, and it is exp ected mote pro cesses must b e evicted. Therefore, ev- not to o ccur more than once or twice. ery pro cess must have the notion of a home ma- In Clouds, migration takes place with ob- chine, which is the machine from which the user ject granularity. That is, as a thread pro- invoked the pro cess. ceeds, it mayinvoke ob jects on di erent no des. Solaris MC provides remote execution and A thread's path of execution ncessarily crosses pro cess migration mechanisms. User must ex- through all of these no des. It is strategic place- plicitly call the rexec system call to carry out ment of ob jects that would b e used as a mech- remote execution. Unlike Plan 9, the destina- anism for load balancing. tion no de need not be sp eci ed. Pro cess mi- Since there are no address space asso ciated gration is assumed to be used mainly for o - with each of the threads, ob jects on remote or loading pro cesses from a no de b eing shutdown lo cal no de can b e invoked with the same seman- for mainteanance.
Load more

Recommended publications
  • Clustering with Openmosix
    Clustering with openMosix Maurizio Davini (Department of Physics and INFN Pisa) Presented by Enrico Mazzoni (INFN Pisa) Introduction • What is openMosix? – Single-System Image – Preemptive Process Migration – The openMosix File System (MFS) • Application Fields • openMosix vs Beowulf • The people behind openMosix • The openMosix GNU project • Fork of openMosix code 12/06/2003 HTASC 2 The openMosix Project MileStones • Born early 80s on PDP-11/70. One full PDP and disk-less PDP, therefore process migration idea. • First implementation on BSD/pdp as MS.c thesis. • VAX 11/780 implementation (different word size, different memory architecture) • Motorola / VME bus implementation as Ph.D. thesis in 1993 for under contract from IDF (Israeli Defence Forces) • 1994 BSDi version • GNU and Linux since 1997 • Contributed dozens of patches to the standard Linux kernel • Split Mosix / openMosix November 2001 • Mosix standard in Linux 2.5? 12/06/2003 HTASC 3 What is openMOSIX • Linux kernel extension (2.4.20) for clustering • Single System Image - like an SMP, for: – No need to modify applications – Adaptive resource management to dynamic load characteristics (CPU intensive, RAM intensive, I/O etc.) – Linear scalability (unlike SMP) 12/06/2003 HTASC 4 A two tier technology 1. Information gathering and dissemination – Support scalable configurations by probabilistic dissemination algorithms – Same overhead for 16 nodes or 2056 nodes 2. Pre-emptive process migration that can migrate any process, anywhere, anytime - transparently – Supervised by adaptive
    [Show full text]
  • Load Balancing Experiments in Openmosix”, Inter- National Conference on Computers and Their Appli- Cations , Seattle WA, March 2006 0 0 5 4 9
    Machine Learning Approach to Tuning Distributed Operating System Load Balancing Algorithms Dr. J. Michael Meehan Alan Ritter Computer Science Department Computer Science Department Western Washington University Western Washington University Bellingham, Washington, 98225 USA Bellingham, Washington, 98225 USA [email protected] [email protected] Abstract 2.6 Linux kernel openMOSIX patch was in the process of being developed. This work concerns the use of machine learning techniques (genetic algorithms) to optimize load 2.1 Load Balancing in openMosix balancing policies in the openMosix distributed The standard load balancing policy for openMosix operating system. Parameters/alternative algorithms uses a probabilistic, decentralized approach to in the openMosix kernel were dynamically disseminate load balancing information to other altered/selected based on the results of a genetic nodes in the cluster. [4] This allows load information algorithm fitness function. In this fashion optimal to be distributed efficiently while providing excellent parameter settings and algorithms choices were scalability. The major components of the openMosix sought for the loading scenarios used as the test load balancing scheme are the information cases. dissemination and migration kernel daemons. The information dissemination daemon runs on each 1 Introduction node and is responsible for sending and receiving The objective of this work is to discover ways to load messages to/from other nodes. The migration improve the openMosix load balancing algorithm. daemon receives migration requests from other The approach we have taken is to create entries in nodes and, if willing, carries out the migration of the the /proc files which can be used to set parameter process. Thus, the system is sender initiated to values and select alternative algorithms used in the offload excess load.
    [Show full text]
  • HPC with Openmosix
    HPC with openMosix Ninan Sajeeth Philip St. Thomas College Kozhencheri IMSc -Jan 2005 [email protected] Acknowledgements ● This document uses slides and image clippings available on the web and in books on HPC. Credit is due to their original designers! IMSc -Jan 2005 [email protected] Overview ● Mosix to openMosix ● Why openMosix? ● Design Concepts ● Advantages ● Limitations IMSc -Jan 2005 [email protected] The Scenario ● We have MPI and it's pretty cool, then why we need another solution? ● Well, MPI is a specification for cluster communication and is not a solution. ● Two types of bottlenecks exists in HPC - hardware and software (OS) level. IMSc -Jan 2005 [email protected] Hardware limitations for HPC IMSc -Jan 2005 [email protected] The Scenario ● We are approaching the speed and size limits of the electronics ● Major share of possible optimization remains with software part - OS level IMSc -Jan 2005 [email protected] Hardware limitations for HPC IMSc -Jan 2005 [email protected] How Clusters Work? Conventional supe rcomputers achieve their speed using extremely optimized hardware that operates at very high speed. Then, how do the clusters out-perform them? Simple, they cheat. While the supercomputer is optimized in hardware, the cluster is so in software. The cluster breaks down a problem in a special way so that it can distribute all the little pieces to its constituents. That way the overall problem gets solved very efficiently. - A Brief Introduction To Commodity Clustering Ryan Kaulakis IMSc -Jan 2005 [email protected] What is MOSIX? ● MOSIX is a software solution to minimise OS level bottlenecks - originally designed to improve performance of MPI and PVM on cluster systems http://www.mosix.org Not open source Free for personal and academic use IMSc -Jan 2005 [email protected] MOSIX More Technically speaking: ● MOSIX is a Single System Image (SSI) cluster that allows Automated Load Balancing across nodes through preemptive process migrations.
    [Show full text]
  • Introduction Course Outline Why Does This Fail? Lectures Tutorials
    Course Outline • Prerequisites – COMP2011 Data Organisation • Stacks, queues, hash tables, lists, trees, heaps,…. Introduction – COMP2021 Digital Systems Structure • Assembly programming • Mapping of high-level procedural language to assembly COMP3231/9201/3891/9283 language – or the postgraduate equivalent (Extended) Operating Systems – You are expected to be competent Kevin Elphinstone programmers!!!! • We will be using the C programming language – The dominant language for OS implementation. – Need to understand pointers, pointer arithmetic, explicit 2 memory allocation. Why does this fail? Lectures • Common for all courses (3231/3891/9201/9283) void func(int *x, int *y) • Wednesday, 2-4pm { • Thursday, 5-6pm *x = 1; *y = 2; – All lectures are here (EE LG03) – The lecture notes will be available on the course web site } • Available prior to lectures, when possible. void main() – The lecture notes and textbook are NOT a substitute for { attending lectures. int *a, *b; func(a,b); } 3 4 Tutorials Assignments • Assignments form a substantial component of • Start in week 2 your assessment. • A tutorial participation mark will • They are challenging!!!! – Because operating systems are challenging contribute to your final assessment. • We will be using OS/161, – Participation means participation, NOT – an educational operating system attendance. – developed by the Systems Group At Harvard – Comp9201/3891/9283 students excluded – It contains roughly 20,000 lines of code and comments • You will only get participation marks in your enrolled tutorial. 5 6 1 Assignments Assignments • Assignments are in pairs • Don’t under estimate the time needed to do the – Info on how to pair up available soon assignments. • We usually offer advanced versions of the – ProfQuotes: [About the midterm] "We can't keep you working assignments on it all night, it's not OS.“ Ragde, CS341 – Available bonus marks are small compared to amount of • If you start a couple days before they are due, you will be late.
    [Show full text]
  • The Utility Coprocessor: Massively Parallel Computation from the Coffee Shop
    The Utility Coprocessor: Massively Parallel Computation from the Coffee Shop John R. Douceur, Jeremy Elson, Jon Howell, and Jacob R. Lorch Microsoft Research Abstract slow jobs that take several minutes without UCop be- UCop, the “utility coprocessor,” is middleware that come interactive (15–20 seconds) with it. Thanks to makes it cheap and easy to achieve dramatic speedups the recent emergence of utility-computing services like of parallelizable, CPU-bound desktop applications using Amazon EC2 [8] and FlexiScale [45], which rent com- utility computing clusters in the cloud. To make UCop puters by the hour on a moment’s notice, anyone with a performant, we introduced techniques to overcome the credit card and $10 can use UCop to speed up his own low available bandwidth and high latency typical of the parallel applications. networks that separate users’ desktops from a utility One way to describe UCop is that it effectively con- computing service. To make UCop economical and easy verts application software into a scalable cloud service to use, we devised a scheme that hides the heterogene- targeted at exactly one user. This goal entails five re- ity of client configurations, allowing a single cluster to quirements. Configuration transparency means the ser- serve virtually everyone: in our Linux-based prototype, vice matches the user’s application, library, and con- the only requirement is that users and the cluster are us- figuration state. Non-invasive installation means UCop ing the same major kernel version. works with a user’s existing file system and application This paper presents the design, implementation, and configuration.
    [Show full text]
  • Legoos: a Disseminated, Distributed OS for Hardware Resource
    LegoOS: A Disseminated, Distributed OS for Hardware Resource Disaggregation Yizhou Shan, Yutong Huang, Yilun Chen, and Yiying Zhang, Purdue University https://www.usenix.org/conference/osdi18/presentation/shan This paper is included in the Proceedings of the 13th USENIX Symposium on Operating Systems Design and Implementation (OSDI ’18). October 8–10, 2018 • Carlsbad, CA, USA ISBN 978-1-939133-08-3 Open access to the Proceedings of the 13th USENIX Symposium on Operating Systems Design and Implementation is sponsored by USENIX. LegoOS: A Disseminated, Distributed OS for Hardware Resource Disaggregation Yizhou Shan, Yutong Huang, Yilun Chen, Yiying Zhang Purdue University Abstract that can fit into monolithic servers and deploying them in datacenters is a painful and cost-ineffective process that The monolithic server model where a server is the unit often limits the speed of new hardware adoption. of deployment, operation, and failure is meeting its lim- We believe that datacenters should break mono- its in the face of several recent hardware and application lithic servers and organize hardware devices like CPU, trends. To improve resource utilization, elasticity, het- DRAM, and disks as independent, failure-isolated, erogeneity, and failure handling in datacenters, we be- network-attached components, each having its own con- lieve that datacenters should break monolithic servers troller to manage its hardware. This hardware re- into disaggregated, network-attached hardware compo- source disaggregation architecture is enabled by recent nents. Despite the promising benefits of hardware re- advances in network technologies [24, 42, 52, 66, 81, 88] source disaggregation, no existing OSes or software sys- and the trend towards increasing processing power in tems can properly manage it.
    [Show full text]
  • Architectural Review of Load Balancing Single System Image
    Journal of Computer Science 4 (9): 752-761, 2008 ISSN 1549-3636 © 2008 Science Publications Architectural Review of Load Balancing Single System Image Bestoun S. Ahmed, Khairulmizam Samsudin and Abdul Rahman Ramli Department of Computer and Communication Systems Engineering, University Putra Malaysia, 43400 Serdang, Selangor, Malaysia Abstract: Problem statement: With the growing popularity of clustering application combined with apparent usability, the single system image is in the limelight and actively studied as an alternative solution for computational intensive applications as well as the platform for next evolutionary grid computing era. Approach: Existing researches in this field concentrated on various features of Single System Images like file system and memory management. However, an important design consideration for this environment is load allocation and balancing that is usually handled by an automatic process migration daemon. Literature shows that the design concepts and factors that affect the load balancing feature in an SSI system are not clear. Result: This study will review some of the most popular architecture and algorithms used in load balancing single system image. Various implementations from the past to present will be presented while focusing on the factors that affect the performance of such system. Conclusion: The study showed that although there are some successful open source systems, the wide range of implemented systems investigated that research activity should concentrate on the systems that have already been proposed and proved effectiveness to achieve a high quality load balancing system. Key words: Single system image, NOWs (network of workstations), load balancing algorithm, distributed systems, openMosix, MOSIX INTRODUCTION resources transparently irrespective of where they are available[1].The load balancing single system image Cluster of computers has become an efficient clusters dominate research work in this environment.
    [Show full text]
  • SEMINARIS DOCENTS DE CASO 03/04 - 2Q NÚM GRUP: Facultat D´Informàtica De Barcelona - Departament AC - UPC
    SEMINARIS DOCENTS DE CASO 03/04 - 2Q NÚM GRUP: Facultat d´Informàtica de Barcelona - Departament AC - UPC Fitxa corresponent al treball sobre un tema d´actualitat dins del tema 6 del curs. Aquest treball també portarà associada una presentació obligatoria del mateix (d’uns 10’) i forma part de la nota NS tal com es va indicar a principi de curs. Aquest treball es pot fer en grups d’1, 2 o 3 persones. Cada grup serà responsable de supervisar l’adequació de la presentació d’un altre grup. El fet de lliurar aquest treball implica l´acceptació de fer-ne una presentació d’un màxim de 10’ a classe a partir de les transparències powerpoint que podran ser distribuïdes com a documentació docent als alumnes de CASO i formar part dels coneixements evaluables de l´assignatura . ELECCIÓ TREBALL: Cal que envieu un mail (amb el format especificat a l´avís del Racó) amb títol de la presentació, els noms, preferència matí/tardai breu descripció a [email protected] . Tot això abans del dimarts 18 de Maig 2004. Després d´aquesta data ja no s'acceptaran. LLIURAMENT: El termini de lliurament dels treballs és fins diumenge 23 de Maig 2004. Els treballs es lliuraran per correu elect rònic a l´adreça [email protected] preferiblement en format PDF. Tamb é es pot enviar en powerpoint usant la plantilla que podeu trobar a http://docencia.ac.upc.es/FIB/CASO/seminaris/TransSEMcaso.ppt o OpenOffice. Tot treball no lliurat dins del termini establert es considerarà no lliurat. PRESENTACIONS ANTERIORS: http://docencia.ac.upc.es/FIB/CASO/seminaris/SeminarisCASO.htm MEMBRES
    [Show full text]
  • Study of Mosix Software Tool for Cluster Computing in Linux
    ISSN (Online) 2278-1021 ISSN (Print) 2319 5940 International Journal of Advanced Research in Computer and Communication Engineering Vol. 4, Issue 10, October 2015 Study of Mosix Software Tool for Cluster Computing In Linux Vinayak D. Shinde1, Priyanka Tarmale2, Shahista shaikh3 H.O.D., Department of Computer Engineering, Shree L.R. Tiwari College of Engineering, Mumbai, India1 Student of M.E, Department of computer Engineering, Shree L.R. Tiwari College of Engineering, Mumbai, India2, 3 Abstract: Mosix conveniently supports a multi-user time-sharing environment for the execution of both sequential and parallel task. it is designed to respond to variations in the resource usage among the nodes by migrating processes from one node to another. Mosix use for load-balancing and to prevent memory depletion from any node .The core of the Mosix technology is the potential of multiple servers (nodes) to work cooperatively. Mosix is a system for sustaining cluster computing. It consists of kernel-level, adaptive resource sharing algorithms that are setup for superiority, overhead-free scalability and ease-of-use of a scalable computing cluster of a single system. It is consider as a leader in the field of high performance computing community. Keywords: Cluster computing, Mosix Technology, scalability in Mosix. 1. INTRODUCTION The mosix technology provide more than two nodes goal is to improve overall (cluster -wide) performance and work combine as they were part of single system. In order to create a convenient lot of different users, townhouse to understand what Mosix does, let us compare a Shared environment for the execution of both sequential and Memory (SMP) multicomputer and a CC.
    [Show full text]
  • Process Migration in Distributed Systems
    Process Migration in Distributed Systems Shek Lun Ho Computer Science Department University of Southern California Los Angeles, CA90007 [email protected] Process Migration is the ability of a system (operating system or user-space program) to transfer processes between different nodes in a network. The motivations behind process migration are to balance load, improve availability, enhance communication performance and ease system administration[13]. However, since a process involves and interacts with many different components of an operating system, migration of a process is technically complicated and demands a great deal of researches. This paper presents key concepts of process migration, design and implementation issues, and illustrates these concepts by several case studies on the typical implementations – MOSIX, Sprite, Condor and V. 1. Introduction Process Migration has been in the computer science literature for more than two decades. One of the earliest concept papers introduces programs that can span machine boundaries in search of free machine for executions as “worms”[3]. Subsequent papers refine the concept of process migration as a potential mean to share processing power and other resources among multiple processors. Numerous papers and implementations have been proposed to introduce process migration on different architectures such as symmetric multiprocessors, Non-Uniform Memory Access (NUMA) multiprocessor, Massively Parallel Processors (MPP) and Local Area Network (LAN) of computers. A process is an operating system (OS) entity of a program in execution. Associated with it are address space and other OS internal attributes such as home directory, open file descriptors, user id, program counter and so on. Process migration is defined as the transfer of a process between different nodes connected by a network.
    [Show full text]
  • Using Mosix for Wide-Area Compuational Resources
    Using Mosix for Wide-Area Compuational Resources 1 By Brian G. Maddox Open-File Report 2004-1091 1 USGS Mid-Continent Mapping Center, Rolla, MO, 65401 U.S. Department of the Interior U.S. Geological Survey 1 Contents Key Words ............................................................................................................................................1 Abstract.................................................................................................................................................1 Introduction ..........................................................................................................................................2 Background ..........................................................................................................................................2 Beowulf.............................................................................................................................................2 Mosix.................................................................................................................................................3 Wine Is Not an Emulator................................................................................................................4 Emulators..........................................................................................................................................5 Methods and Testing..........................................................................................................................5 Discussion
    [Show full text]
  • Open-MPI Over MOSIX Parallel Computing in a Clustered World
    Open-MPI over MOSIX Parallel Computing in a Clustered World ∗ y z Adam Lev-Libfeld, Supervised by: Amnon Barak and Alex Margolin School of Computer Science and Engineering The Hebrew University of Jerusalem, Israel September 14, 2009 Abstract Recent increased interest in Cloud computing emphasizes the need to find an adequate solution to the load-balancing problem in parallel comput- ing - efficiently running several jobs concurrently on a cluster of shared computers (nodes). One approach to solve this problem is by preemp- tive process migration- the transfer of running processes between nodes. A possible drawback of this approach is the increased overhead between heavily communicating processes. This project presents a solution to this last problem by incorporating the process migration capability of MOSIX into Open-MPI and by reducing the resulting communication overhead. Specifically, we developed a module for direct communication (DiCOM) between migrated Open-MPI processes, to overcome the increased com- munication latency of TCP/IP between such processes. The outcome is reduced run-time by improved resource allocation. This document is Open Source Secure: Written from scratch in Emacs on a Unix machine using LATEX version 2" ∗[email protected], ID 200226983, Corresponding author. [email protected] [email protected] To Dad Acknowledgments Special thanks to Amnon Shiloh for the extensive help in all MOSIX related issues. Thanks to Tal Maoz, Tal Ben-Nun and the System group for the moral and technical support. All graphs, graphics, diagrams and charts, as well as any other artworks in this document is the result of the original work of the author unless mentioned otherwise.
    [Show full text]