Browse Prior Art Database

Method for Off-Line Dynamic Control of Agent Process Pool Size for a Database Manager Server

IP.com Disclosure Number: IPCOM000105106D
Original Publication Date: 1993-Jun-01
Included in the Prior Art Database: 2005-Mar-19
Document File: 2 page(s) / 50K

Publishing Venue

IBM

Related People

Chang, DY: AUTHOR [+3]

Abstract

In the Database Manager Distributed Database System version 2.0 (DBM 2.0), many DBM Agent processes may service requests from one or more database applications. If the DBM system becomes overloaded with data base requests, it would be useful to dynamically add more database service agents to handle the load. Disclosed is the mechanism in place to accomplish this DBM system load control.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 58% of the total text.

Method for Off-Line Dynamic Control of Agent Process Pool Size for a Database Manager Server

      In the Database Manager Distributed Database System version 2.0
(DBM 2.0), many DBM Agent processes may service requests from one or
more database applications.  If the DBM system becomes overloaded
with data base requests, it would be useful to dynamically add more
database service agents to handle the load.  Disclosed is the
mechanism in place to accomplish this DBM system load control.

      In the Database Manager Distributed Database System version
2.0, there is a set of Database Agent processes (the DBM Agent Pool)
which service the database requests on behalf of the application
programs.  Each DBM Agent process may service requests from any of
the applications at any time.

      In a DBM server, there may be a great many application
processes, both local and remote, making database requests to only a
few DBM Agent processes and these requests may start to back up on
the request queue.  The only way to reduce the database request
backlog and increase throughput is to add more DBM Agent processes to
the Agent Pool to handle the surge in database activity.  When there
is relatively little database activity, these extra DBM Agent
processes have no requests to service and should be terminated so as
to reduce the server processing overhead.

      This disclosure describes one of the facilities provided by DBM
2.0 which allow the load balancing, as outl...