Browse Prior Art Database

AUTOMATIC LAUNCHING OF APPLICATIONS WITH LOAD BALANCING BASED ON CURRENT LOAD AND "POTENTIAL" LOAD

IP.com Disclosure Number: IPCOM000008642D
Original Publication Date: 1998-Mar-01
Included in the Prior Art Database: 2002-Jul-01
Document File: 2 page(s) / 86K

Publishing Venue

Motorola

Related People

Vaidyanathan Chandramowleeswaran: AUTHOR [+2]

Abstract

In a distributed system, where applications are installed on one or more servers. a central controller is needed to manage the resources. The controller has knowledge of all the applications and the servers that have them installed. In such a system, launching an application can be automatic and can be done without the client having to mount the server's filesystem through NFS. Also, on such systems, load balancing can be done in a lot of different ways. This document explains one such unique way that takes into account not just the current load on the various servers but also the "potential" load that it carries.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 50% of the total text.

Page 1 of 2

0 M

MOTOROLA Technical Developments

AUTOMATIC LAUNCHING OF APPLICATIONS WITH LOAD BALANCING BASED ON CURRENT LOAD AND "POTENTIAL" LOAD

by Vaidyanathan Chandramowleeswaran and Chee Ma

  In a distributed system, where applications are installed on one or more servers. a central controller is needed to manage the resources. The controller has knowledge of all the applications and the servers that have them installed. In such a system, launching an application can be automatic and can be done without the client having to mount the server's filesystem through NFS. Also, on such systems, load balancing can be done in a lot of different ways. This document explains one such unique way that takes into account not just the current load on the various servers but also the "potential" load that it carries.

  The central controller is made known the instal- lation of any new application through a registration process. Each application reports its own "load" information to the controller. This includes the memory and CPU utilization factors and the "poten- tial" load that it adds to the server when it is installed. The term "potential" load refers to the load that this application can add to this server when it is started. Thus the controller can effectively choose the perfect candidate whenever a request for an application comes in.

  The controller, on getting an application request, determines the load on all servers that has the application installed and returns the name of the server that has the least load (current + potential).

The requesting process then contacts that server directly requesting that this application be started and displayed back to the terminal where the request originated.

The advantages to this scheme are the following:

1. The...