JP2008004125A - Load control method and apparatus, and processing program thereof - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the following problem: in a load distribution method for distributing to job-processing apparatuses by a load distribution apparatus, a request is assigned to each of the job-processing apparatuses in a uniform manner, and therefore, for example, when there exist a plurality of jobs which differ in their execution loads including DB processing or the like, processing of light-load jobs is delayed as requests for processing of heavy-load jobs increase. <P>SOLUTION: When a load in time of execution of an execution target job can be expected by adding a determination function for the job with analysis of the URL requested from a client, an upper limit value is set to the number of job execution processes to control the load of DB processing or the like in job units. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

The present invention relates to a load control technique for controlling the load balance of each resource according to a condition when there are a plurality of usable resources.

The conventional load balancing control method uses the technology disclosed in Patent Document 1, and matches the usage status of resources for each business such as batch, online, and TSS (time sharing system) executed in the computer system. To distribute the load.

JP-A-9-167141

Since the load balancing control method of the prior art is for each usage pattern of the computer system such as batch, online, and TSS, when the usage pattern of the computer system is the same (for example, online), regardless of the processing content, There arises a problem that the load distribution control becomes uniform.

An object of the present invention is to perform load distribution control according to each of a plurality of purposes using a resource group.

To prevent delays in the processing of lightly-loaded jobs in a business processing device or system that processes the business requested by one or more clients over the network, by performing business processing that places a heavy load on each business common database In addition, it is possible to control the load on each business common database by predetermining the business to be requested from the request URL sent from the client and arbitrarily setting the upper limit number of processing for each business. .

Also, the number of requests for high-load work from the client is recorded in URL units, the step of determining the requested work from the URL, the number of business processes being executed and the number of business processes are compared, and the business process If the limit is reached, the request is temporarily queued and waited. If the job execution condition is satisfied, the request is passed to the job processing device. The response time from the job processing device is used. By having a step to calculate the average execution time, it became possible to control the load on the common DB.

For a plurality of purposes using a resource group, it becomes possible to perform load distribution control according to each of the purposes.

FIG. 1 is an overall configuration diagram for explaining the present invention. Reference numeral 100 denotes a client that makes a business process request. The client is connected to 110 load control devices via the 101 network. The load control device 110 includes a request registration unit 111, a load limiting unit 11
2, processing result registration unit 113, request information DB (114), restriction information DB (115), wait queue
It consists of 116. Reference numeral 117 denotes a load balancer that distributes requests to 120 business processing device groups. Reference numeral 121 denotes a business unit, which is processed by the business processing device 120.
There may be a case where a plurality of tasks 121 are processed simultaneously in one task processing device 120. 130 is a common DB used by each business processing device 120, and there may be a plurality of DBs. When a business process request is requested from a browser or the like of the client 100, the request first enters the request registration unit 111 of the load control device 110. The request registration unit 111 updates the request information DB according to the contents of the arrived request URL.

The request information DB has a table as shown in FIG. 201 is U for processing DB
RL path name. Reference numeral 202 denotes a business name existing in the business processing apparatus 120. 203 is the number of requests being executed, and indicates how many requests registered in 201 are currently being executed by the business processing device 120. 204 is the average response time by URL, and the URL
The average time from the start to the end of the process is recorded.

The processing of the request registration unit 111 is shown in FIG. When a request arrives at the load control device 110, the URL is analyzed (step 400). Thereafter, the request information DB is accessed, and the value of the number of requests being executed for the URL is incremented by 1 (step 401). Also, the target business name is determined from the request URL (step 402), and the URL and the target business name are passed to the load limiting unit 112 (step 403). The load limiting unit 112 works to suppress the number of business process executions in consideration of the current number of requests and the load on the common DB (130). The load restriction unit 112 updates the restriction information DB (115).

The restriction information DB (115) has a table as shown in FIG. 301 is the business name,
302 is a processing limit number that sets a limit on the maximum number of requests for each business, 303 is the total number of processing requests that is the total number of current processing requests, and 304 is the maximum allowable response time returned to the client. This is the latest response time that is the maximum value of the slow response time, and 305 is the average response time for each task that is the average value of the response times for each current task.

The processing of the load limiting unit 112 is shown in FIG. When the target business is input from the request registration unit 111 (step 500), if the total processing request number 303 of the business has reached the processing limit number 302 or more, the request is temporarily stored in the waiting queue 116, and the total processing request number Wait for 103 to fall below the processing limit 302 and proceed to the next process (Step 5).
01). In step 502, if the current average response time 305 for business exceeds the latest response time 304, the request is stored in the waiting queue 116 and waits for the average response time 305 for business to decrease. Otherwise, the value of the task of the total processing request count 303 in the restriction information DB (115) is incremented by 1, and the request is passed to the load balancer 117. The load balancer 117 is connected to each business processing device 120.
Throw requests equally. The business processing device 120 executes the given business 121. The business 121 accesses and processes the common DB 130 as necessary, and returns the processing result to the client 100. As a process thereof, the processing result registration unit 113 of the load control device 110 is used.
Return to. The processing result registration unit 113 has a function of calculating the time elapsed from the request to the business processing device to the response and recording the load status of the common DB.

The processing of the processing result registration unit 113 is shown in FIG. The request information DB (114) is accessed, and the average response time 204 for each URL is calculated and updated (step 600). Further, the number of requests 203 being executed is reduced by 1 (step 601). Next, the control information DB is accessed, the total processing request number 303 for the business is reduced by 1 (step 602), and the business-specific average response time 305 is calculated and updated (step 603). Thereafter, the result is returned to the client (step 604), and the series of operations is completed.

As explained above, by temporarily limiting requests flowing into the business processing device and common DB for each business, the load on the business processing device and common DB due to heavy business can be reduced. It becomes possible not to give load to other sensitive business processing. As a result, it is possible to improve the response of a business with a small load.

1 is an overall configuration diagram showing an embodiment of the present invention. It is a table of request information DB. It is a table of restriction information DB. It is a flowchart of the request registration part of this invention. It is a flowchart of the load limiting part of this invention. It is a flowchart of the process result registration part of this invention.

Explanation of symbols

100: Client
101: Network
110: Load control device
111: Request registration section
112: Load limiting section
113: Processing result registration section
114: Request information DB
115: Restriction information DB
116: Wait queue
117: Load balancer
120: Business processing device
121: Business
130: Common DB
200: Request information DB table
201: URL path name
202: Business name
203: Number of execution requests
204: Average response time by URL (s)
300: Restriction information DB table
301: Business name
302: Processing limit
303: Total number of execution requests
304: Latest response time
305: Average response time by business (s)

Claims (12)

In a load control method for processing a plurality of business processes required by a terminal with a plurality of computers,
Associating the location information of the program related to the business processing with the business name, storing the processing limit number in association with each business in advance,
In response to an input of a request including the location information of the program, if the number of processes related to the program does not exceed the processing limit number, the process is executed for the request, and if it exceeds, the process is accumulated in the queue. A load control method.   2. The load control method according to claim 1, wherein the position information is a URL. 2. The load control method according to claim 1, wherein the business process is a shared database. 2. The load control method according to claim 1, wherein when the request is processed, the number of processes counted up is stored in association with the processing limit number. In a load control method for processing a plurality of business processes required by a terminal with a plurality of computers,
The location information of the program related to the business process is associated with the business name, and the upper limit value of the response is stored in association with each business in advance,
In response to an input of a request including the location information of the program, if the average response of the work related to the program does not exceed the upper limit value of the response, the process is performed on the request, and if exceeded, it is queued A load control method characterized by accumulating. The load control method according to claim 5, wherein after processing the request, an average response is calculated and stored in association with an upper limit value of the response.   The load control method according to claim 5, wherein the position information is a URL. The load control method according to claim 5, wherein the business process is a shared database. In a load control device for processing a plurality of business processes required by a terminal with a plurality of computers,
Means for associating the location information of the program related to the business process with a business name, and storing the process limit number in advance for each business;
In response to an input of a request including the location information of the program, if the number of processes related to the program does not exceed the processing limit number, the process is executed for the request, and if it exceeds, the process is accumulated in the queue. And a load control device. In a load control device for processing a plurality of business processes required by a terminal with a plurality of computers,
Means for associating the location information of the program related to the business process with the business name, and storing the upper limit value of the response in association with each business in advance;
In response to an input of a request including the location information of the program, if the average response of the work related to the program does not exceed the upper limit value of the response, the process is performed on the request, and if exceeded, it is queued And a load control device. In a load control program for processing multiple business processes required by a terminal with multiple computers,
Associating position information of a program related to the business process with a business name, and storing in advance a process limit number for each business;
In response to an input of a request including the location information of the program, if the number of processes related to the program does not exceed the processing limit number, the process is executed for the request, and if it exceeds, the process is accumulated in the queue. A load control program comprising steps. In a load control program for processing multiple business processes required by a terminal with multiple computers,
Associating the location information of the program related to the business process with a business name, and storing the upper limit value of the response in association with each business in advance;
In response to an input of a request including the location information of the program, if the average response of the work related to the program does not exceed the upper limit value of the response, the process is performed on the request, and if exceeded, it is queued A load control program comprising the step of accumulating.

Images