Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /home/zhenxiangba/zhenxiangba.com/public_html/phproxy-improved-master/index.php on line 456
US7480719B2 - Information system, load control method, load control program and recording medium - Google Patents
[go: Go Back, main page]

US7480719B2 - Information system, load control method, load control program and recording medium - Google Patents

Information system, load control method, load control program and recording medium Download PDF

Info

Publication number
US7480719B2
US7480719B2 US10/577,174 US57717404A US7480719B2 US 7480719 B2 US7480719 B2 US 7480719B2 US 57717404 A US57717404 A US 57717404A US 7480719 B2 US7480719 B2 US 7480719B2
Authority
US
United States
Prior art keywords
resource
predesignated
application
transaction
processing time
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related, expires
Application number
US10/577,174
Other languages
English (en)
Other versions
US20070157210A1 (en
Inventor
Masashi Inoue
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kyndryl Inc
Original Assignee
International Business Machines Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by International Business Machines Corp filed Critical International Business Machines Corp
Assigned to INTERNATIONAL BUSINESS MACHINES CORPORATION reassignment INTERNATIONAL BUSINESS MACHINES CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: INOUE, MASASHI
Publication of US20070157210A1 publication Critical patent/US20070157210A1/en
Application granted granted Critical
Publication of US7480719B2 publication Critical patent/US7480719B2/en
Assigned to KYNDRYL, INC. reassignment KYNDRYL, INC. ASSIGNMENT OF ASSIGNOR'S INTEREST Assignors: INTERNATIONAL BUSINESS MACHINES CORPORATION
Adjusted expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
    • H04L41/5096—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/48—Indexing scheme relating to G06F9/48
    • G06F2209/482—Application
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99931—Database or file accessing
    • Y10S707/99932—Access augmentation or optimizing
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99951—File or database maintenance
    • Y10S707/99952—Coherency, e.g. same view to multiple users
    • Y10S707/99953—Recoverability

Definitions

  • the present invention relates to an information system, a load control method, a load control program and a recording medium. Specifically, the present invention relates to an information system that includes a plurality of application servers and a database server for performing load control, and a load control method, a load control program and a recording medium therefor.
  • Patent Document 1 Japanese Patent Laid-Open Publication No. 2001-160040
  • Patent Document 2 Japanese Patent Laid-Open Publication No. 2000-268012
  • a large-scale information system is constituted by a plurality of application servers and one or multiplexed database servers.
  • the application server executes a corresponding application for the Web page, and transmits, in return, data for the Web page to the terminal, including the execution results.
  • the database server accesses a database upon receiving a database access request from the application server.
  • the loads imposed on the server program and the server computer are maintained at a constant level or lower, and the control process can not be performed based on the response time relative to the transaction. Further, a load control process that is appropriate for both the application servers and the database server can not be performed.
  • One objective of the present invention is to provide an information system, a load control method, a load control program and a recording medium that can resolve the above problems.
  • an information system that includes a plurality of application servers, each of which can execute at least one application program for processing a transaction from a terminal, and a database server for accessing a database based on a request received from any one of the plurality of application servers, comprising:
  • a process time monitoring unit for monitoring processing periods of time required for the application program to process a transaction received by an application server
  • a bottleneck identification unit for identifying, based on monitoring results of processing periods, a bottleneck in at least one of the plurality of application servers if the processing period is not within a predesignated permissible range
  • a load controller for reducing a multiplicity of the application program on an application server identified as having a bottleneck. Also, a load control method, a load control program and a recording medium related to the information system are provided.
  • the appropriate load control processing can be performed in consonance with the processing time required for the transaction on each application server.
  • the configuration of an information system 10 according to this mode is shown in FIG. 1 .
  • the information system 10 according to this mode monitors periods of time required by a plurality of application servers 120 to process transactions, and to process loads imposed on the plurality of application servers 120 and a database server 150 , and employs the monitoring results to perform appropriate load control to resolve bottlenecks for an application server 120 or for the database server 150 . Further, when various types of application programs corresponding to various transactions, are combined and executed, the information system 10 of this mode can appropriately perform load control, so that a factor that contributes to the deterioration of the performance of an application program does not adversely affect the processing performance of another application programs.
  • the information system 10 is a computer system that is to be connected via a network 110 , such as the Internet or an intranet, to a plurality of terminals 100 employed by users that employ the information system 10 .
  • the information system 10 comprises a plurality of the application servers (WASs: Web Application Servers) 120 , a database server (DBS) 150 and a load control server 160 .
  • WASs Web Application Servers
  • DBS database server
  • Each of the plurality of WASs 120 is a server computer that performs at least one application program that includes a Java (registered trademark) servlet or JSPs (Java Server Pages), for processing a transaction, such as an HTTP request, received from the terminals 100 .
  • the WAS 120 also transmits to the terminal 100 , in turn, a Web page that includes execution results.
  • the WAS 120 requests that the DBS 150 access a database (DB) 152 based on an instruction issued by the application program.
  • DB database
  • the DBS 150 is a server computer that accesses the DB 152 based on a request received from any one of the plurality of WASs 120 , and that transmits, in return, the access results to the WAS 120 that is the request source.
  • the load control server 160 monitors the periods of time required by the plurality of WASs 120 to process transactions and the processing loads imposed on the plurality of WASs 120 and the DBS 150 , and provides load control for the information system based on the monitoring results.
  • Each of the plurality of WASs 120 includes an HTTP server 125 , a WEB application server 130 , a process time acquisition unit 140 , a process load acquisition unit 142 and a server load controller 144 .
  • the HTTP server 125 receives a transaction from the terminal 100 , and transmits to the terminal 100 , in return, a Web page corresponding to the transaction.
  • the HTTP server 125 may be operated by a server that is a physically separate unit.
  • the Web application server 130 executes at least one application program 134 in accordance with a transaction received from the terminal 100 .
  • the Web application server 130 provided for each of the plurality of WASs 120 performs a application program 134 , which are selected from a plurality of types of application program 134 and are consonant with the type of transaction received from the terminal 100 .
  • the priority levels to execute on the WAS 120 are designated for the multiple types of application programs 134 . More specifically, the multiple types of application programs 134 are categorized into a plurality of groups in accordance with the priority levels, and are executed at the priority levels designated for the groups to which the individual application programs 134 belong.
  • the Web application server 130 includes a multiplicity controller 132 , a DB access controller 136 and a DB connection pool 138 .
  • the multiplicity controller 132 controls multiplicities by which the plurality of application programs 134 should be executed concurrently.
  • the multiplicity of the application program 134 indicates the maximum number of application programs 134 that are to be executed concurrently, in consonance with a plurality of transactions of the same type that were received at the same time.
  • the DB access controller 136 processes, together, the access requests for the DB 152 issued by the multiple types of application programs 134 . Then, the DB access controller 136 allocates a DB connection 139 for each application program 134 , so that the priority levels of the multiple application programs 134 can be identified on the DBS 150 side. More specifically, the DB access controller 136 is connected to the DBS 150 by employing a user ID that differs for each priority level, so that the priority level of the access request can be identified on the DBS 150 side.
  • the DB connection pool 138 includes a plurality of DB connections 139 .
  • Each of the DB connections 139 serves as a connection juncture for the DBS 150 for issuing a request to access the DB 152 .
  • the multiplicity controller 132 and the DB access controller 136 described above may be obtained in a manner such that a WAS 120 performs a set of class functions, for example, that provides a framework whereby the single WAS 120 combines and efficiently operates the plurality of types of application programs 134 .
  • the process time acquisition unit 140 obtains, from the multiplicity controller 132 and the DB access controller 136 , individual transaction process times, and obtains statistics, for example, for the processing time for each application program 134 and for the database processing time. At this time, the processing time during which the application program 134 process the transaction received from the terminal 100 is also called a transaction response time. When the processing time required by one application program 134 is not within a permissible range, the process time acquisition unit 140 notifies the load control server 160 of a service level deterioration event that indicates a service level has been lowered for the pertinent application program 134 . In this case, the process time acquisition unit 140 may include information, such as the database processing time, in the service level deterioration event to use to notify the load control server 160 .
  • the process load acquisition unit 142 obtains, by employing the performance monitoring function, for example, an operating system operated by the WAS 120 , the amount consumed of one or a plurality of application server resources, which are owned by the WAS 120 and which are resources to be used by the application programs 134 , and obtains statistics for the amounts consumed of the application server resources. Then, when the amount consumed of one application server resource does not fall within a permissible range, the process load acquisition unit 142 notifies the load control server 160 of a system resource, high load event that indicates the processing load for the application server resource is possibly overloaded.
  • the performance monitoring function for example, an operating system operated by the WAS 120
  • the process load acquisition unit 142 notifies the load control server 160 of a system resource, high load event that indicates the processing load for the application server resource is possibly overloaded.
  • the process load acquisition unit 142 may obtain the amount consumed by the application server resource for each application program 134 , and when the amount consumed by the application program 134 does not fall within the permissible range, may provide a notification, for the load control server 160 , of a system resource high load event. Or instead of this, the process load acquisition unit 142 may obtain the total amount consumed by the application server resources for all the application programs 134 , and when the consumed amount is not within the permissible range, may provide a notification, for the load control server 160 , of a system resource high load event.
  • the server load controller 144 performs the load control, imposed on the WAS 120 , in accordance with the load control process performed by the load control server 160 .
  • the server load controller 144 changes the multiplicity of application program 134 .
  • the DBS 150 includes the DB 152 , DB process request I/Fs 153 , a DB engine 154 , a process load acquisition unit 156 and a server load controller 158 .
  • Data to be accessed by the individual application programs 134 are stored in the DB 152 .
  • the plurality of DB process request I/Fs 153 are arranged in consonance with the DB connections 139 , and serve as connection junctures where the WAS 120 issues an access request for the DB 152 .
  • the WAS 120 is connected to the DB process request I/F 153 consonant with a user ID that differs in accordance with the priority level of each of the plurality of application programs 134 . Therefore, based on the user ID, the DBS 150 can identify the priority level of the application program 134 that has issued the access request.
  • the DB engine 154 accesses the DB 152 based on an access request, such as a SQL command, that each of the plurality of WASs 120 has issued based on an instruction for each of the plurality of application programs 134 .
  • the process load acquisition unit 15 obtains, by employing the performance monitoring function of an operating system operated by the DBS 150 , for example, the amount consumed of one or a plurality of database server resources that are owned by the DBS 150 and that are used by the application program 134 to access the DB 152 , and obtains the statistics for the amount consumed of the database server resources.
  • the process load acquisition unit 156 notifies the load control server 160 that a system resource high load event has occurred that indicates the processing load for the database server resource is high.
  • the process load acquisition unit 156 may obtain the amount consumed of the database server resource provided for each DB process request I/F 153 , and when the amount consumed by the corresponding application program 134 is not within the permissible range, may provide a notification for the load control server 160 of a system resource high load event.
  • the process load acquisition unit 156 may obtain the total amount of the database server resources consumed by all the DB process request I/Fs 153 , and when the amount consumed is not within the permissible range, may provide a notification for the load control server 160 of a system resource high load event.
  • the server load controller 158 controls a load imposed on the DBS 150 in accordance with the load control process performed by the load control server 160 . As the load control for the server load controller 158 , the server load controller 158 in this mode changes the priority levels for the DB process request I/Fs 153 for accessing the DB 152 .
  • the load controller 160 includes a process time monitoring unit 165 , a bottleneck identification unit 170 , a process load monitoring unit 190 and a load controller 175 .
  • the process time monitoring unit 165 monitors, for each of the WASs 120 , the processing time required by each application program 134 to process a transaction.
  • the process time monitoring unit 165 employs a service level deterioration event, received from each of the WASs 120 , to detect whether the transaction processing time exceeds the permissible range.
  • the bottleneck identification unit 170 employs the monitoring results obtained for the processing times of transactions on the plurality of WASs 120 to identify a bottleneck in at least one of the WASs 120 or in the DBS 150 .
  • the process load monitoring unit 190 for each of the WASs 120 , monitors the amount consumed by one or a plurality of application server resources and the amount consumed by one or a plurality of database server resources. In this mode, based on the system resource high load events received from the WASs 120 and the DBS 150 , the process load monitoring unit 190 detects whether the amount consumed of an application server resource or a database server resource, identified by the system resource high load event, exceeds the permissible range.
  • the load controller 175 When a bottleneck is identified in at least one of the WASs 120 or the DBS 150 , the load controller 175 performs the load control process to remove the bottleneck from the server whereat the bottleneck has been identified.
  • the load controller 175 includes a load control information storage unit 177 , a load control information acquisition unit 179 and a load control processor 181 .
  • load control information for designating the load control process to be performed by the load control processor 181 of the load controller 175 , is stored, in correlation with the server that has been identified as having a bottleneck and a resource that has been detected as being a high load for the pertinent server.
  • the load control information storage unit 177 stores the groups of application programs 134 , the priority levels of the groups and multiplicity information indicating multiplicities that can be designated for the application programs 134 .
  • the load control information acquisition unit 179 obtains, from the load control information storage unit 177 , load control information that is related to the server identified as having a bottleneck by the bottleneck identification unit 170 , and that is consonant with the resource that has been determined to be a high load by the process load monitoring unit 190 . Thereafter, the load control information acquisition unit 179 outputs the load control information to the load control processor 181 . The load control processor 181 then performs the load control process designated in the load control information in order to remove the bottleneck for the server thus identified. During the load control process, the load control processor 181 transmits a server load control instruction to the server load controller 144 in the WAS 120 or to the server load controller 158 in the DBS 150 , which is a load control target.
  • the transaction processing time required by each of the application servers 120 and the process load imposed on each application server 120 and the database 150 are monitored, and based on the monitoring results, a load control process for removing a bottleneck can be appropriately selected and performed.
  • the bottleneck identification processing performed by the information system 10 in this mode is shown in FIG. 2 .
  • the process time monitoring unit 165 receives, from one or the plurality of WASs 120 , a notification provided for one or a plurality of service level deterioration events, and detects whether the transaction processing time exceeds the permissible range.
  • the bottleneck identification unit 170 identifies the location of a bottleneck based on the monitoring results obtained for the processing times for the plurality of WASs 120 . More specifically, the bottleneck identification unit 170 identifies the location of a bottleneck based on the monitoring results obtained for the processing times for individual application programs 134 for each WAS 120 .
  • a permissible range i.e., permissible processing time range
  • M threshold number of WASs 120
  • the bottleneck identification unit 170 may identify the pertinent WAS(s) 120 (S 220 ) as having a bottleneck.
  • a resource related to a specific entry for a transaction for this application program 134 maybe identified as a bottleneck (S 230 ).
  • the threshold value for the number of WAS 120 is smaller than the number of WASs 120 , and may be designated in advance, for example, by the administrator of the information system 10 .
  • the DBS 150 is identified as having a bottleneck, which is a common resource for the entire information system 10 .
  • the bottleneck identification unit 170 may identify the DBS 150 (S 260 ) as having a bottleneck. Or when the processing times required by the other types of transaction are within the permissible range (S 250 : No), a resource related to a transaction consonant with the pertinent application program 134 may be identified as a bottleneck (S 270 ).
  • the bottleneck identification unit 170 in this mode performs the above described processing either for each application program 134 or for each group of application programs 134 . That is, under a condition wherein the processing time required by one application program 134 or by one of the application programs 134 belonging to a group is not within the permissible range, the bottleneck identification unit 170 identifies a bottleneck in a WAS 120 for the pertinent application program 134 , or in one of the application programs 134 that belong to the pertinent group. More specifically, when the processing time required by one application program 134 or the application programs belonging to one group does not fall within the permissible range for equal to or smaller than the threshold number of WASs 120 , the bottleneck identification unit 170 identifies a bottleneck in these WASs 120 . As for more than the threshold number of the WASs 120 , when the process time required either by one application program 134 or by the application programs belonging to one group exceeds a predesignated permissible range, the DBS 150 is identified as having a bottleneck.
  • the WAS(s) 120 for which the processing time does not fall within the predesignated permissible range can be identified as having a bottleneck. More specifically, the bottleneck identification unit 170 identifies the WAS(s) 120 as having a bottleneck under a condition wherein the number of the WASs 120 , for which the processing time does not fall within the permissible range, is equal to or smaller than a threshold value. When the number of WASs 120 for which the processing time does not fall within the permissible range exceeds the threshold value, the DBS 150 can be identified as having a bottleneck.
  • the bottleneck identification unit 170 identifies this WAS 120 as having a bottleneck.
  • the threshold value is, for example, 1, and when the number of WASs 120 for which the processing time does not fall within the permissible range is one, the bottleneck identification unit 170 identifies this WAS 120 as having a bottleneck.
  • the threshold value is, for example, (the number of WASs 120 - 1 ), and when the processing times for all the WASs 120 do not fall within the permissible range, the DBS 150 is identified as having a bottleneck.
  • these WASs 120 can be identified as having a bottleneck.
  • the information system 10 can determine whether the service level for a specific WAS 120 has been lowered, or whether the DBS 150 used in common by the entire information system 10 has become a bottleneck that can cause the deterioration of the service levels of multiple WASs 120 , and can appropriately identify the location of the bottleneck.
  • the bottleneck identification unit 170 may employ a condition other than S 210 or S 250 , etc., to designate a more detailed location of the bottleneck.
  • the permissible range of the processing times may be determined based, for example, on the following predesignated reference. Specifically, when a predesignated number or more of transactions are processed by certain application program 134 during a predesignated period, such as sixty seconds, and when the processing time required by the application program 134 to process a predesignated ratio, such as 50%, of the transactions exceeds the permissible processing time, the process time monitoring unit 165 determines that the processing time required by the application program 134 exceeds the permissible range.
  • the permissible processing time is defined by adding an offset time, which is determined based on a standard deviation, to the average processing times per transaction during peak loads during a period, such as the past month.
  • the high load determination method employed by the information system 10 in this mode is shown in FIG. 3 .
  • the process load acquisition unit 142 and the process load acquisition unit 156 detect the imposition of a high load on these resources. And when the detection of a high load imposed on the pertinent resource is performed while the condition, such as the number of times, designated by the “determination condition” is satisfied, the amount of the resource consumed exceeds the permissible range (i.e., permissible load range) and the high load state is determined. Then, a system resource high load event for the pertinent resource is transmitted to the process load monitoring unit 190 .
  • a system resource high load cancel event indicating that a high load is no longer imposed on the pertinent resource, is transmitted to the process load monitoring unit 190 .
  • the process load monitoring unit 190 determines that the high load is no longer imposed on the system resource.
  • the process load acquisition unit 156 employs the “detection condition”, the “determination condition” and the “cancel condition” to determine whether a high load is imposed on each of a plurality of database server resources, each of which are described as a “resource used in common (DBS)” in the “type of location of bottleneck” column.
  • the process load acquisition unit 156 in this mode employs the conditions to determine whether a high load is imposed on each of a plurality of database server resources, including a processor, a disk, a memory and a database buffer.
  • a processor there are a disk to store a database, a disk to store the access log of the DB 152 and a disk to store a file other than the database and the access log, and the process load acquisition unit 156 detects a high load when the usage rate for the database resource is “equal to or more than x% for n seconds, on average”.
  • the process load acquisition unit 156 determines that a high load has been imposed on the database resource, and transmits a system resource high load event to the process load monitoring unit 190 . Further, when the high load state is not repeatedly detected f times after the system resource high load event has been transmitted to the process load monitoring unit 190 , the process load acquisition unit 156 transmits a system resource high load cancel event to the process load monitoring unit 190 .
  • the process load acquisition unit 156 performs a notification for the system resource high load event and the system resource high load cancel event for these database server resources, in the same manner as for the system resource high load event and the system resource high load cancel event for the processor, etc.
  • the process load acquisition unit 142 on each WAS 120 employs the “detection condition”, the “determination condition” and the “cancel condition” to determine whether a high load has been imposed on each of a plurality of application server resources, which are described using “WAS” in the “type of location of bottleneck” column.
  • the process load acquisition unit 142 in this mode employs the “detection condition”, the “determination condition” and the “cancel condition” to determine whether a high load has been imposed on each database server resource, such as a processor, a disk, a memory and a JVM (Java Virtual Machine) memory and on each of a plurality of application servers, including DB connections.
  • database server resource such as a processor, a disk, a memory and a JVM (Java Virtual Machine) memory
  • the process load acquisition unit 142 performs the detection of a high load and the transmission of an event for the processor, the disk and the memory. Further, when the JVM, which executes various programs or modules constituting the web application sever 130 , performs “garbage collection equal to or more than x times, for n seconds”, the process load acquisition unit 142 assumes that a memory allocated to the JVM is too small and detects a high load. And the process load acquisition unit 142 transmits a notification for a system resource high load event and a system resource high load cancel event for the JVM memory, in the same manner as for the notification of the system resource high load event and the system resource high load cancel event for the processor, etc.
  • the process load acquisition unit 142 assumes that the DB connections are insufficient and detects a high load.
  • the process load acquisition unit 142 detects that a high load has been imposed on the DB connections, the process load acquisition unit 142 transmits a system resource high load event to the process load monitoring unit 190 , and until the pertinent WAS 120 is halted, does not transmit to the process load monitoring unit 190 a notification indicating that a high load is no longer imposed.
  • the process load acquisition unit 142 employs the “detection condition”, the “determination condition” and the “cancel condition” to determine whether, due to the affect of the process of the application program 134 , a high load has been imposed on each of the resources, such as the processor of the WAS 120 , the processor of the DBS 150 and the disk of the DBS 150 , which are described as the “resources related to the transaction” in the “type of location of bottleneck” column.
  • the process load acquisition unit 142 assumes that the rate of the processing time required by the processor of the WAS 120 is high, and detects a high load. And when a high load is detected, the process load acquisition unit 142 transmits a system resource high load event to the process load monitoring unit 190 . When the state indicated by the detection condition does not occur for n seconds, a system resource high load cancel event is transmitted to the process load monitoring unit 190 .
  • the process load acquisition unit 142 assumes that the rate of the process time required by the processor of the DBS 150 is high, and detects a high load.
  • the process load acquisition unit 142 transmits a system resource high load event to the process load monitoring unit 190 .
  • a system resource high load cancel event is transmitted to the process load monitoring unit 190 .
  • the process load monitoring unit 190 determines that a high load has been imposed on the processor of the DBS 150 in consonance with the transaction. Further, in the same manner as for the processor of the DBS 150 , the process load acquisition unit 142 determines that a high load has been imposed on the disk of the DBS 150 in consonance with the transaction.
  • the process load monitoring unit 190 employs the system resource high load event and the system resource high load cancel event described above as examples to determine whether a high load has been imposed on each of a plurality of resources owned by each of the WASs 120 and the DBS 150 .
  • the process load monitoring unit 190 may hold the “detection condition”, the “determination condition” and the “cancel condition”, which correspond to each of the resources, as files, for example, stored in the storage devices of the load control server 160 , and these conditions may be changed based on an instruction entered by the administrator of the information system 10 , etc.
  • the bottleneck identification unit may identify more precisely an application program 134 that causes a bottleneck.
  • load control information stored in the load control information storage unit 177 is shown in FIG. 4 .
  • the load control information storage unit 177 stores load control information for designating a load control process that the load controller 175 should perform when a bottleneck is identified in a server that owns the pertinent resource, and when the amount consumed of the resource is not within a predesignated permissible range.
  • the load control information storage unit 177 may store at least one set of load control information, information for designating a plurality of load control processes and the priority rankings for the load control processes.
  • the load control information acquisition unit 179 identifies the pertinent resource as a bottleneck.
  • the load control information acquisition unit 179 obtains load control information stored in the load control information storage unit 177 . More specifically, when a bottleneck is identified in a WAS 120 , the load control information acquisition unit 179 obtains load control information stored in the load control information storage unit 177 , in correlation with one of a plurality of application server resources owned by the WAS 120 , and the amount that has been consumed is determined by the process load monitoring unit 190 to not be within the permissible range.
  • the load control information storage unit 179 obtains load control information stored in the load control information storage unit 177 , in correlation with one of a plurality of database server resources, the amount of which has been consumed is determined by the process load monitoring unit 190 to not be within the permissible range.
  • the load control processor 181 performs the load control process designated by the load control information that is obtained by the load control information acquisition unit 179 .
  • the load control processor 181 performs another load control process having a lower priority rank than the specific load control process designated by the load control information. In this manner, when the bottleneck is not resolved by using one type of load control process, the load control processor 181 can perform another load control process, so that the bottleneck can be removed more effectively.
  • the load control processor 181 in this mode performs the following load control processes.
  • the load control processor 181 reduces multiplicities of the application programs 134 of a group having a lower priority level than the application programs 134 for which it has been determined that the processing time is not within the permissible range. More specifically, the load control processor 181 obtains from the bottleneck identification unit 170 , via the load control acquisition unit 179 , a plurality of group identifiers for groups that have lower priority levels than an application program 134 , for which it has been determined that the processing time is not within the permissible range. Then, the load control processor 181 designates the obtained group identifiers, and transmits an instruction to the server load controller 144 to reduce the multiplicities of other application programs 134 that have lower priority levels than the application program 134 . Upon receiving this instruction, the server load controller 144 reduces the maximum value that indicates the number of application programs 134 that the multiplicity controller 132 operates concurrently, so that the multiplicities of the other application programs 134 can be reduced.
  • the load control processor 181 performs the above described load control process 1 for each of the WASs 120 included in the information system 10 . Therefore, the load control processor 181 can reduce the multiplicities according to which all the WASs 120 accept transactions, and can reduce accordingly the total amount of transactions processed by the information system 10 , so that the number of accesses for the DB 152 can be reduced.
  • the load control processor 181 performs a greater reduction of the priority level of the process for accessing the DB 152 based on a request received from the application programs 134 of a group having a lower priority level than an application program 134 for which the processing time is determined to not be within the permissible range. More specifically, the load control processor 181 obtains from the bottleneck identification unit 170 , via the load control information acquisition unit 179 , a plurality of group identifiers for groups that have lower priority levels than an application program 134 for which the processing time has been determined to not be within the permissible range.
  • the load control processor 181 designates the obtained group identifiers, and transmits an instruction to the server load controller 158 to reduce the priority levels for accessing the DB 152 based on requests from the other application programs 134 that have lower priority levels than the first application program 134 has.
  • the server load controller 158 reduces the process execution priority levels of the corresponding DB process request I/Fs 153 .
  • the load control processor 181 When the bottleneck identification unit has identified, by using a system resource high load event, an application program 134 that causes a high load to be imposed on the resource that is a bottleneck in a server wherein the bottleneck is present, the load control processor 181 reduces the multiplicity of the group the application program 134 belongs to. More specifically, the load control processor 181 obtains from the bottleneck identification unit 170 , via the load control information acquisition unit 179 , the group identifier of a group for the application program 134 that causes a bottleneck. Then, the load control processor 181 designates the obtained group identifier, and transmits an instruction to the server load controller 144 to reduce the multiplicity of the pertinent application program 134 . Upon receiving this instruction, the server load controller 144 reduces the maximum value that indicates the number of application programs 134 that the multiplicity controller 132 operates concurrently, so that the multiplicity of the other application program 134 is reduced.
  • the load control processor 181 performs the above described load control process 3 for each of the plurality of WASs 120 included in the information system 10 .
  • the load control processor 181 can reduce the multiplicities of all the WASs 120 that accept transactions, and accordingly, can reduce the total number of transactions processed by the information system 10 , so that the number of accesses of the DB 152 can be reduced.
  • the load control processor 181 When the bottleneck identification unit 170 has identified, by using a system resource high load event, an application program 134 that causes a high load to be imposed on the resource that is a bottleneck in a server wherein the bottleneck is present, the load control processor 181 reduces the priority level of a process for accessing the DB 152 , based on a request issued by application programs 134 of a group that executes the pertinent application program 134 . More specifically, the load control processor 181 obtains from the bottleneck identification unit 170 , via the load control information acquisition unit 179 , the group identifier of an application program 134 that has caused a bottleneck.
  • the load control processor 181 designates the obtained group identifier, and transmits an instruction to the server load controller 158 to reduce the priority level of a process for accessing the DB 152 , based on a request from the application programs 134 in the group that the pertinent application program 134 belongs to.
  • the server load controller 158 reduces the process execution priority level of the corresponding DB process request I/F.
  • the load control processor 181 reduces the multiplicity of an application program 134 for which the processing time has been determined not to be within the permissible range. More specifically, the load control processor 181 obtains from the bottleneck identification unit 170 , via the load control information acquisition unit 179 , the group identifier of an application program 134 for which the processing time has been determined to not be within the permissible range. Then, the load control processor 181 designates the group identifier of the application program 134 , and transmits an instruction to the server load controller 144 to reduce the multiplicity of the pertinent application program 134 . Upon receiving this instruction, the server load controller 144 decrements the maximum value that indicates the number of application programs 134 the multiplicity controller 132 operates concurrently, so that the multiplicities for the execution of the application programs 134 can be reduced.
  • the load control processor 181 performs the above control process 3 , in the same manner as the load control process 1 , for each of the plurality of WASs 120 included in the information system 10 .
  • the load control processor 181 reduces the priority level of a process for accessing the DB 152 , based on a request received from an application program 134 for which the processing time has been determined not to be within the permissible range. More specifically, the load control processor 181 obtains from the bottleneck identification unit 170 , via the load control information acquisition unit 179 , the group identifier of an application program 134 for which the processing time has been determined not to be within the permissible range. Then, the load control processor 181 designates the group identifier of the pertinent application program 134 , and transmits an instruction to the server load controller 158 to reduce the priority level of the process for accessing the DB 152 , based on the request received by the application program 134 . Upon receiving this instruction, the server load controller 158 reduces the process execution priority level of the corresponding DB process request I/F 153 .
  • the load control information shown in FIG. 4 is stored in the load control information storage unit 177 , depending on whether the amount consumed of one of the database server resources exceeds the permissible range.
  • the load control information storage unit 177 stores load control information indicating that the load process processes 3 , 1 , 4 , 2 , 5 and 6 are to be performed in this priority order. Further, in correlation with when the amount consumed of a disk on which the database is stored exceeds the permissible range, the load control information storage unit 177 stores load control information indicating that the load control processes 2 , 1 , 6 and 5 are to be performed in this priority order. Furthermore, when the amount consumed of a disk on which the access log is stored exceeds the permissible range, the load control information storage unit 177 stores load control information indicating that the load control processes 1 , 2 , 5 and 6 are to be performed in this priority order.
  • the load control information storage unit 177 stores load control information indicating that the load control processes 1 and 5 are to be performed in this priority order.
  • the load controller 175 When, for example, a bottleneck is identified in the DBS 150 , and further, when the amount consumed of the processor resource exceeds the permissible range and the processor is identified as a bottleneck, and an application program 134 , for which the amount consumed of the processor resource of the DBS 150 is not within the permissible range, can be identified, the load controller 175 performs the load control process 3 by employing the load control information. Then, the load controller 175 reduces the multiplicities for which the WAS 120 executes the pertinent application program 134 and the application programs 134 that belong to the same the group as this application program 134 .
  • the load controller 175 When the bottleneck in the DBS 150 is not resolved through this load control process, the load controller 175 performs the load control process 1 , so that the multiplicities can be reduced for which the WAS 120 executes other application programs 134 that belong to the other groups having a lower priority level than that of the pertinent application program 134 .
  • the load controller 175 reduces the amount of processing performed by the application program 134 that greatly consumes the processor resource, to attempt to reduce the load imposed on the DBS 150 .
  • the amount of processing performed by an application program 134 that has a priority level lower than that of the pertinent application program 134 is reduced, so that the load imposed on the DBS 150 can be gradually lowered.
  • the load controller 175 sequentially performs the load control processes 4 and 2 , so that it reduces the adverse effect of another process handling requests on the DBS 150 , and it attempts to increase the service level. So long as this is not a problem for the application program 134 for which the processing time is initially determined not to be within the permissible range, or a problem for an application program 134 that has a higher priority level, it is presumed that the bottleneck can be removed by using the above mentioned load control.
  • the load control process 5 can be performed to reduce the multiplicity with which the WAS 120 executes the application program 134 for which the service level is lowered, so that the load imposed on the DBS 150 can be further reduced.
  • the load controller 175 performs the load control process 6 , and reduces the priority level of the processes for accessing the DB 152 , based on requests received from the application program 134 . As a result, the adverse affect that a request handled by the DBS 150 provides for another process can be reduced.
  • the load controller 175 When, for another example, a bottleneck is identified in the DBS 150 and a disk on which a database is stored is identified as a bottleneck, and when an application program 134 , for which the amount consumed of the disk resource for the DBS 150 is not within the permissible range is identified, the load controller 175 performs the load control process 2 . Then, the load controller 175 reduces the priority level of the processes for accessing the DB 152 , based on requests by application programs 134 that belong to a group having a lower priority level than that of the pertinent application program 134 .
  • the load controller 175 reduce the priority level of the processes for accessing the DB 152 , based on requests by an application program 134 that belongs to a group having a lower priority level than that of the pertinent application group 134 and that employs a disk on which the database used by the pertinent application program 134 is stored.
  • the load controller 175 sequentially performs the load control processes 1 , 6 and 5 until the bottleneck in the DBS 150 has been resolved.
  • the load control information shown in FIG. 4 is stored in the load control information storage unit 177 , depending on whether the amount consumed of one of a plurality of application server resources exceeds the permissible range.
  • the load control information storage unit 177 stores load control information indicating that the load process processes 3 , 1 and 5 are to be performed in this priority order. Further, in correlation with when the memory, the disk(s), the JVM memory and the DB connections exceed the permissible range, the load control information storage unit 177 stores load control information indicating that the load control processes 1 and 5 are to be performed.
  • the load controller 175 When, for example, a bottleneck is identified in the WAS 120 , and further, when the amount consumed of the processor resource exceeds the permissible range and the processor is identified as a bottleneck, and an application program 134 , for which the amount consumed of the processor resource of the WAS 120 is not within the permissible range, can be identified, the load controller 175 performs the load control process 3 by employing the load control information. Then, the load controller 175 reduces the multiplicities with which the WAS 120 executes the pertinent application program 134 and the application programs 134 that belong to the same the group as this application program 134 .
  • the load controller 175 When the bottleneck in the WAS 120 is not resolved by using this load control process, the load controller 175 performs the load control process 1 , so that the multiplicities can be reduced with which the WAS 120 executes other application programs 134 that belong to a group having a lower priority level than the pertinent application program 134 .
  • the load controller 175 can perform the load control process 5 to reduce the multiplicity with which the WAS 120 executes the application program 134 for which the service level is lowered, so that the load imposed on the DBS 150 can be further reduced.
  • the load control information storage unit 177 in this mode stores load control information indicating that the load control process 5 should be performed when the amount consumed of the processor resource of the WAS 120 exceeds the permissible range.
  • the load control information storage unit 177 stores load control information indicating that the load control processes 5 and 6 should be performed in this priority order when the amount consumed of the processor resource or of the disk of the DBS 150 exceeds the permissible range.
  • FIG. 5 is a diagram showing an example hardware configuration for a computer 900 according to the mode of the present invention.
  • the computer 900 according to this mode functions, for example, as a load control server 160 by executing a load control program.
  • the computer 900 comprises: a CPU peripheral section, including a CPU 1000 , a RAM 1020 , a graphic controller 1075 and a display device 1080 that are interconnected by a host controller 1082 ; an input/output section, including a communication interface 1030 , a storage device 1040 and a CD-ROM drive 1060 that are connected to the host controller 1082 by an input/output controller 1084 ; and a legacy input/output section, including a ROM 1010 , a flexible disk drive 1050 and an input/output chip 1070 that are connected to the input/output controller 1084 .
  • the host controller 1082 connects the RAM 1020 to the CPU 1000 , which accesses the RAM 1020 at a high transfer rate, and the graphic controller 1075 .
  • the CPU 1000 is operated based on programs stored in the ROM 1010 and the RAM 1020 , and controls the individual sections.
  • the graphic controller 1075 obtains image data that the CPU 1000 generates in a frame buffer in the RAM 1020 and displays as image data on the display device 1080 .
  • the graphic controller 1075 may internally include a frame buffer for storing image data generated, for example, by the CPU 1000 .
  • the input/output controller 1084 connects the host controller 1082 to the communication interface 1030 , which is a comparatively fast input/output device, the storage device 1040 and the CD-ROM drive 1060 .
  • the communication interface 1030 communicates with an external device via a network.
  • the storage device 1040 stores programs and data used by the computer 900 .
  • the CD-ROM drive 1060 reads programs or data from a CD-ROM 1095 and provides the programs or data for the storage device 1040 .
  • the ROM 1010 and comparatively slow input/output devices are connected to the input/output controller 1084 .
  • the ROM 1010 includes, for example, a boot program that is executed when the computer 900 is activated and programs that depend on the hardware of the computer 900 .
  • the flexible disk drive 1050 reads a program or data from a flexible disk 1090 , and provides the program or the data for the storage device 1040 via the RAM 1020 .
  • the input/output chip 1070 connects the flexible disk drive 1050 , or various types of input/output devices, via a parallel port, a serial port, a keyboard port and a mouse port, for example.
  • Programs provided for the computer 900 , via the RAM 1020 , are recorded on a flexible disk 1090 , in the CD-ROM 1095 or on another recording medium, such as an IC card, and are to be employed by a user.
  • the programs that permit the WAS 120 to function as the HTTP server 125 , the Web application server 130 , the process time acquisition unit 140 , the process load acquisition unit 142 and the server load controller 144 are read from a recording medium, are installed in the WAS 120 via the communication interface 1030 , and are executed by a server computer that is employed as the WAS 120 .
  • the programs that permit the DBS 150 to function as the DB 152 , the DB process request I/F 153 , the process load acquisition unit 156 and the server load controller 158 are read from a recording medium, may be installed in the DBS 150 via the communication interface 1030 and the load control server 160 , and are executed by a server computer that are employed as the DBS 150 .
  • the load control program that permits the computer 900 to function as the load control server 160 is read from a recording medium, and is installed in the storage device 1040 of the computer 900 , and is executed by the CPU 1000 .
  • the programs installed in the WASs 120 includes: an HTTP server program; a Web application server program including a multiplicity control module and a DB access control module; a process time acquisition module; a process load acquisition module; and a server load control module. These programs and modules permit individual WASs 120 to serve as the HTTP server 125 , the Web application server 130 that includes the multiplicity controller 132 and the DB access controller 136 , the process time acquisition unit 140 , the process load acquisition unit 142 and the server load controller 144 .
  • the programs installed in the DBS 150 include: a DB engine program, a process load acquisition module and a server load control module. These programs and modules permit the DBS 150 to serve as the DB engine 154 , the process load acquisition unit 156 and the server load controller 158 .
  • the load control program which is installed in the computer 900 and which permits the computer 900 to function as the load control server 160 , includes: a process time monitoring module, a bottleneck identification module, a process load monitoring module, and a load control module that includes a load control information acquisition module and a load control process module.
  • This program and these modules permit the computer 900 to function as the process time monitoring unit 165 , the bottleneck identification unit 170 , the process load monitoring unit 190 and the load controller 175 , which includes the load control information acquisition unit 179 and the load control processor 181 .
  • This storage medium may not only be a flexible disk 1090 or a CD-ROM 1095 , but can also be an optical recording medium, such as a DVD or a PD, a magneto-optical recording medium, such as an MD, a tape medium, or a semiconductor memory, such as an IC card.
  • a storage device such as a hard disk or a RAM, provided for a server system connected to a special communication network or the Internet may be employed as a recording medium.
  • a program may be provided for the computer 900 via the network, and then be transmitted from the computer 900 via the load control server 160 to the WAS 120 or the WEB application server 130 .
  • the load control information storage unit 177 can store appropriate load control processes in correlation with the location of a bottleneck and the resource identified as having a high load. And based on load control information stored in the load control information storage unit 177 , the load controller 175 can appropriately perform the load control process, e.g., can change the multiplicity of the application program 134 to be executed by the WAS 120 or can change the priority level of the process for accessing the DB 152 .
  • the multiplicity whereby each of the application programs 134 is to be executed and the priority level of an access of the DBS 150 can be appropriately changed in accordance with the processing time required by each of the plurality of application programs 134 . Therefore, in a case wherein various types of application systems are operated concurrently by the information system 10 , deterioration of the service level provided by a specific application program 134 due to the abnormal consumption of system resources by another application program 134 can be automatically detected, and the service level can be automatically returned to the normal state within a short period of time.
  • an information system 10 can be provided that has the same robustness as when various types of application programs 134 are performed by separate information systems 10 .
  • FIG. 1 Shows a configuration for an information system 10 according to one mode of the present invention.
  • FIG. 2 Shows a bottleneck identification process performed by the information system 10 according to the mode of the present invention.
  • FIG. 3 Shows a high load determination method employed by the information system 10 according to the mode of the present invention.
  • FIG. 4 Shows example load control information stored in a load control information storage unit 177 according to the mode of the present invention.
  • FIG. 5 Shows an example hardware configuration of a computer 900 according to the mode of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Debugging And Monitoring (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)
US10/577,174 2003-10-29 2004-10-27 Information system, load control method, load control program and recording medium Expired - Fee Related US7480719B2 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
JP2003368773 2003-10-29
JP2003-368773 2003-10-29
PCT/JP2004/015902 WO2005041038A1 (ja) 2003-10-29 2004-10-27 情報システム、負荷制御方法、負荷制御プログラム及び記録媒体

Publications (2)

Publication Number Publication Date
US20070157210A1 US20070157210A1 (en) 2007-07-05
US7480719B2 true US7480719B2 (en) 2009-01-20

Family

ID=34510356

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/577,174 Expired - Fee Related US7480719B2 (en) 2003-10-29 2004-10-27 Information system, load control method, load control program and recording medium
US12/351,277 Active 2028-11-13 US8386611B2 (en) 2003-10-29 2009-01-09 Information system, load control method, load control program and recording medium

Family Applications After (1)

Application Number Title Priority Date Filing Date
US12/351,277 Active 2028-11-13 US8386611B2 (en) 2003-10-29 2009-01-09 Information system, load control method, load control program and recording medium

Country Status (10)

Country Link
US (2) US7480719B2 (ja)
EP (1) EP1679595A4 (ja)
JP (1) JP4205103B2 (ja)
KR (1) KR100866857B1 (ja)
CN (1) CN100465900C (ja)
BR (1) BRPI0416101A (ja)
CA (1) CA2541576C (ja)
IL (1) IL174874A0 (ja)
MX (1) MXPA06004071A (ja)
WO (1) WO2005041038A1 (ja)

Cited By (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060195579A1 (en) * 2005-02-28 2006-08-31 International Business Machines Corporation Method and system for managing server load to execute transactions of an application program on multiple servers
US20080082977A1 (en) * 2006-09-29 2008-04-03 Microsoft Corporation Automatic load and balancing for virtual machines to meet resource requirements
US20080172671A1 (en) * 2007-01-11 2008-07-17 International Business Machines Corporation Method and system for efficient management of resource utilization data in on-demand computing
US20080195447A1 (en) * 2007-02-09 2008-08-14 Eric Bouillet System and method for capacity sizing for computer systems
US20090031019A1 (en) * 2007-07-27 2009-01-29 Burr Michael J Technique for Graphically Displaying Application Processing Time Distributions in Real-Time
US20090089418A1 (en) * 2007-10-01 2009-04-02 Ebay Inc. Method and system to detect a network deficiency
US20090133031A1 (en) * 2003-10-29 2009-05-21 Masashi Inoue Information system, load control method, load control program and recording medium
US20100058234A1 (en) * 2008-08-29 2010-03-04 Contactual, Inc. Networked contact center user interface
US20100054448A1 (en) * 2008-08-29 2010-03-04 Contactual, Inc. Systems and methods for selection of a communicatoin path
US20100054451A1 (en) * 2008-08-29 2010-03-04 Contactual, Inc. Limiting contact in a networked contact center environment
US20100057927A1 (en) * 2008-08-29 2010-03-04 Contactual, Inc. Methods and systems for information streaming to user interface
US20100054439A1 (en) * 2008-08-29 2010-03-04 Contactual, Inc. Methods and systems for multilayer provisioning of networked contact centers
US20100054450A1 (en) * 2008-08-29 2010-03-04 Contactual, Inc. Networked contact center
US20100262971A1 (en) * 2008-07-22 2010-10-14 Toyota Jidosha Kabushiki Kaisha Multi core system, vehicular electronic control unit, and task switching method
US20100268816A1 (en) * 2009-04-17 2010-10-21 Hitachi, Ltd. Performance monitoring system, bottleneck detection method and management server for virtual machine system
US20110307889A1 (en) * 2010-06-11 2011-12-15 Hitachi, Ltd. Virtual machine system, networking device and monitoring method of virtual machine system
US20120054251A1 (en) * 2010-09-01 2012-03-01 Fujitsu Limited Data distributing apparatus, data storing device, and recording medium
US8468545B2 (en) 2010-08-18 2013-06-18 8X8, Inc. Interaction management
US20150074262A1 (en) * 2013-09-12 2015-03-12 Vmware, Inc. Placement of virtual machines in a virtualized computing environment
US10997051B2 (en) 2018-06-01 2021-05-04 TmaxSoft Co., Ltd. Server, method of controlling server, and computer program stored in computer readable medium therefor
US20210224263A1 (en) * 2019-02-08 2021-07-22 Intuit Inc. Graph database applications

Families Citing this family (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005309703A (ja) * 2004-04-21 2005-11-04 Yokogawa Electric Corp 電子機器システム
JP2007264921A (ja) * 2006-03-28 2007-10-11 Fujitsu Ltd 性能情報採取プログラム及び装置
US9081605B2 (en) * 2007-03-27 2015-07-14 Nec Corporation Conflicting sub-process identification method, apparatus and computer program
US8627327B2 (en) * 2007-10-24 2014-01-07 International Business Machines Corporation Thread classification suspension
US7930489B2 (en) * 2008-03-28 2011-04-19 Symantec Corporation Techniques for optimizing configuration partitioning
JP5343586B2 (ja) * 2009-01-29 2013-11-13 富士通株式会社 情報処理装置、情報処理方法及びコンピュータプログラム
JP5482052B2 (ja) * 2009-09-24 2014-04-23 富士通株式会社 観測分析装置および観測分析方法
US8640139B2 (en) * 2009-10-29 2014-01-28 Nec Corporation System deployment determination system, system deployment determination method, and program
CN101777009B (zh) * 2009-11-30 2012-12-19 英业达股份有限公司 应用程序的负载控管方法
EP2615511A1 (de) * 2012-01-12 2013-07-17 Siemens Aktiengesellschaft Verfahren zur synchronen Ausführung von Programmen in einem redundanten Automatisierungssystem
JP2013171347A (ja) * 2012-02-17 2013-09-02 Fujitsu Frontech Ltd 情報処理装置、サーバ検出方法、及びプログラム
US8856887B2 (en) 2012-07-09 2014-10-07 Ping Identity Corporation Methods and apparatus for delegated authentication token retrieval
US9274854B2 (en) * 2012-07-27 2016-03-01 International Business Machines Corporation Contamination based workload management
US9438488B2 (en) * 2012-11-09 2016-09-06 Citrix Systems, Inc. Systems and methods for appflow for datastream
WO2014118792A1 (en) * 2013-01-31 2014-08-07 Hewlett-Packard Development Company, L.P. Physical resource allocation
US8613055B1 (en) * 2013-02-22 2013-12-17 Ping Identity Corporation Methods and apparatus for selecting an authentication mode at time of issuance of an access token
US9495199B2 (en) * 2013-08-26 2016-11-15 International Business Machines Corporation Management of bottlenecks in database systems
KR102165460B1 (ko) 2013-11-27 2020-10-14 삼성전자 주식회사 전자 장치 및 전자 장치의 메모리 관리 방법
CN104331406A (zh) * 2013-12-20 2015-02-04 乐视网信息技术（北京）股份有限公司 一种数据库容量控制方法及装置
JP6233141B2 (ja) * 2014-03-28 2017-11-22 沖電気工業株式会社 データベースシステム、データベースサーバ、データベースサーバプログラム、データベースクライアント及びデータベースクライアントプログラム
CN105335142B (zh) * 2014-07-29 2019-03-15 国际商业机器公司 在事务处理系统中标识事务的性能瓶颈的方法和装置
CN105704175B (zh) * 2014-11-25 2019-03-19 阿里巴巴集团控股有限公司 一种连接建立方法和装置
CN104683463B (zh) * 2015-02-28 2019-01-25 北京京东尚科信息技术有限公司 一种应用服务器的控制方法和装置以及服务器系统
GB201504612D0 (en) 2015-03-18 2015-05-06 Inquisitive Systems Ltd Forensic analysis
CN105227374B (zh) * 2015-10-23 2018-05-29 浪潮(北京)电子信息产业有限公司 一种集群应用的故障迁移方法和系统
US11947978B2 (en) 2017-02-23 2024-04-02 Ab Initio Technology Llc Dynamic execution of parameterized applications for the processing of keyed network data streams
US10831509B2 (en) 2017-02-23 2020-11-10 Ab Initio Technology Llc Dynamic execution of parameterized applications for the processing of keyed network data streams
GB201708671D0 (en) 2017-05-31 2017-07-12 Inquisitive Systems Ltd Forensic analysis
US20200065313A1 (en) 2018-08-27 2020-02-27 Box, Inc. Extensible content object metadata
US11669793B2 (en) * 2019-10-01 2023-06-06 Box, Inc. Inter-application workflow performance analytics
US12154052B2 (en) 2019-10-02 2024-11-26 Box, Inc. Cross-enterprise workflow adaptation
US11681572B2 (en) 2019-12-23 2023-06-20 Box, Inc. Extensible workflow access
US20210294661A1 (en) * 2020-03-19 2021-09-23 Entertainment Technologists, Inc. TASK MANAGEMENT OF LARGE COMPUTING WORKLOADS in A CLOUD SERVICE AGGREGATED FROM DISPARATE, RESOURCE-LIMITED, PRIVATELY CONTROLLED SERVER FARMS
US11606392B2 (en) * 2020-05-29 2023-03-14 Mcafee, Llc System for tuning a device having security software for security and performance
US11861029B2 (en) 2020-09-14 2024-01-02 Box Inc. Workflow execution state variables
KR20220101789A (ko) * 2021-01-12 2022-07-19 삼성전자주식회사 전자 장치 및 전자 장치의 동작 방법

Citations (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS57757A (en) 1980-06-04 1982-01-05 Hitachi Ltd Job execution schedule system
JPH11282695A (ja) 1998-03-11 1999-10-15 Internatl Business Mach Corp <Ibm> 多重システム・クラスタ内のサ―バの数を制御する方法及び装置
JP2000268012A (ja) 1999-03-12 2000-09-29 Nec Corp クライアントサーバシステムにおけるサーバ負荷の分散方法ならびに装置
WO2001013228A2 (en) 1999-08-13 2001-02-22 Sun Microsystems, Inc. Graceful distribution in application server load balancing
JP2001160040A (ja) 1999-12-01 2001-06-12 Nec Corp サーバ多重度制御装置、サーバ多重度制御方法およびサーバ多重度制御プログラムを記録した記録媒体
WO2001042908A2 (en) 1999-12-10 2001-06-14 Art Technology Group, Inc. Method and system for load balancing and management
US6381617B1 (en) * 1999-08-25 2002-04-30 Hewlett-Packard Company Multiple database client transparency system and method therefor
US20030028583A1 (en) 2001-07-31 2003-02-06 International Business Machines Corporation Method and apparatus for providing dynamic workload transition during workload simulation on e-business application server
US6615253B1 (en) * 1999-08-31 2003-09-02 Accenture Llp Efficient server side data retrieval for execution of client side applications
JP2003298655A (ja) 2002-04-05 2003-10-17 Nippon Telegr & Teleph Corp <Ntt> サイト領域内ボトルネック特定方法
US6950848B1 (en) * 2000-05-05 2005-09-27 Yousefi Zadeh Homayoun Database load balancing for multi-tier computer systems
US6965938B1 (en) * 2000-09-07 2005-11-15 International Business Machines Corporation System and method for clustering servers for performance and load balancing
US7051330B1 (en) * 2000-11-21 2006-05-23 Microsoft Corporation Generic application server and method of operation therefor
US7069267B2 (en) * 2001-03-08 2006-06-27 Tririga Llc Data storage and access employing clustering
US7146353B2 (en) * 2003-07-22 2006-12-05 Hewlett-Packard Development Company, L.P. Resource allocation for multiple applications
US7281045B2 (en) * 2004-08-26 2007-10-09 International Business Machines Corporation Provisioning manager for optimizing selection of available resources
US7296268B2 (en) * 2000-12-18 2007-11-13 Microsoft Corporation Dynamic monitor and controller of availability of a load-balancing cluster

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0769845B2 (ja) 1987-01-27 1995-07-31 日本電気株式会社 多重ホストシステムのジヨブ多重度管理方式
US5235508A (en) 1990-05-31 1993-08-10 At&T Bell Laboratories Automated resource allocation cutting stock arrangement using random cut patterns
JP3501385B2 (ja) 1995-04-13 2004-03-02 株式会社日立製作所 ジョブ実行順序決定方法
JP2940450B2 (ja) 1995-10-26 1999-08-25 日本電気株式会社 クラスタ型コンピュータのジョブスケジュール方法及び装置
US6859834B1 (en) * 1999-08-13 2005-02-22 Sun Microsystems, Inc. System and method for enabling application server request failover
EP1137295A1 (en) 2000-03-20 2001-09-26 BRITISH TELECOMMUNICATIONS public limited company Communications network
US6485306B1 (en) * 2001-07-10 2002-11-26 Aiptek International Inc. Locus-recordable portable handwriting device
CN1407760A (zh) * 2001-08-31 2003-04-02 高建国际有限公司 便于用户在收看电视时浏览互联网的网络系统和方法
US7007207B2 (en) 2002-10-21 2006-02-28 International Business Machines Corporation Scheduling of transactions in system-level test program generation
US7263555B2 (en) * 2003-04-30 2007-08-28 International Business Machines Corporation Apparatus and method for dynamic sharing of server network interface resources
US7441033B2 (en) * 2003-08-14 2008-10-21 Oracle International Corporation On demand node and server instance allocation and de-allocation
EP1679595A4 (en) 2003-10-29 2008-06-04 Ibm INFORMATION SYSTEM, LOAD CONTROL METHOD AND PROGRAM, AND RECORDING MEDIUM
US7493380B2 (en) 2003-12-02 2009-02-17 International Business Machines Corporation Method for determining load balancing weights using application instance topology information
JP4223411B2 (ja) 2004-01-19 2009-02-12 株式会社日立製作所 実行多重度制御システム、実行多重度制御システムの制御方法、及びプログラム
IL167628A (en) * 2004-06-04 2010-11-30 Optier Ltd System and method for performance management in a multi-tier computing environment
JP2006209165A (ja) 2005-01-25 2006-08-10 Hitachi Ltd 同時実行多重度調整システム及び方法
JP4117299B2 (ja) 2005-02-28 2008-07-16 インターナショナル・ビジネス・マシーンズ・コーポレーション サーバの多重度の上限値を制御するための方法、管理サーバ、サーバ、およびプログラム
US9223622B2 (en) * 2007-03-09 2015-12-29 Hewlett-Packard Development Company, L.P. Capacity planning of multi-tiered applications from application logs
US8374929B1 (en) * 2007-08-06 2013-02-12 Gogrid, LLC System and method for billing for hosted services
US8086596B2 (en) * 2008-05-15 2011-12-27 International Business Machines Corporation Healthcheck of information technology infrastructure based on log data
US8756586B2 (en) * 2009-12-10 2014-06-17 Tata Consultancy Services Limited System and method for automated performance testing in a dynamic production environment
US20120060167A1 (en) * 2010-09-08 2012-03-08 Salsburg Michael A Method and system of simulating a data center

Patent Citations (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS57757A (en) 1980-06-04 1982-01-05 Hitachi Ltd Job execution schedule system
JPH11282695A (ja) 1998-03-11 1999-10-15 Internatl Business Mach Corp <Ibm> 多重システム・クラスタ内のサ―バの数を制御する方法及び装置
JP2000268012A (ja) 1999-03-12 2000-09-29 Nec Corp クライアントサーバシステムにおけるサーバ負荷の分散方法ならびに装置
WO2001013228A2 (en) 1999-08-13 2001-02-22 Sun Microsystems, Inc. Graceful distribution in application server load balancing
US6381617B1 (en) * 1999-08-25 2002-04-30 Hewlett-Packard Company Multiple database client transparency system and method therefor
US6615253B1 (en) * 1999-08-31 2003-09-02 Accenture Llp Efficient server side data retrieval for execution of client side applications
JP2001160040A (ja) 1999-12-01 2001-06-12 Nec Corp サーバ多重度制御装置、サーバ多重度制御方法およびサーバ多重度制御プログラムを記録した記録媒体
WO2001042908A2 (en) 1999-12-10 2001-06-14 Art Technology Group, Inc. Method and system for load balancing and management
US6950848B1 (en) * 2000-05-05 2005-09-27 Yousefi Zadeh Homayoun Database load balancing for multi-tier computer systems
US6965938B1 (en) * 2000-09-07 2005-11-15 International Business Machines Corporation System and method for clustering servers for performance and load balancing
US7051330B1 (en) * 2000-11-21 2006-05-23 Microsoft Corporation Generic application server and method of operation therefor
US7296268B2 (en) * 2000-12-18 2007-11-13 Microsoft Corporation Dynamic monitor and controller of availability of a load-balancing cluster
US7069267B2 (en) * 2001-03-08 2006-06-27 Tririga Llc Data storage and access employing clustering
US20030028583A1 (en) 2001-07-31 2003-02-06 International Business Machines Corporation Method and apparatus for providing dynamic workload transition during workload simulation on e-business application server
JP2003298655A (ja) 2002-04-05 2003-10-17 Nippon Telegr & Teleph Corp <Ntt> サイト領域内ボトルネック特定方法
US7146353B2 (en) * 2003-07-22 2006-12-05 Hewlett-Packard Development Company, L.P. Resource allocation for multiple applications
US7281045B2 (en) * 2004-08-26 2007-10-09 International Business Machines Corporation Provisioning manager for optimizing selection of available resources

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
Czajkowski, Grzegorz et al.; JRES: A Resource Accounting Interface for Java; ACM SIGPLAN Notices, ACM, Association for Computing Machinery, New York, NY, US, vol. 33, No. 10; In Proceedings of the 1998 ACM OOPSLA Conference, Vancouver, BC, Oct. 1998; XP-002469308; ISSN: 0362-1340; pp. 21-35 (15 pages).
Grabs, T. et al., High-level Parallelisation in a Database Cluster: a Feasibility Study Using Document Services. Data Engineering, 2001. Proceedings. 17th International Conference on, Apr. 2001, pp. 121 to 130.
Joines, Stacy et al.; Performance analysis for java Web Sites [Online] Sep. 10, 2002; Addison Weslay Professional, XP-002474287; Retrieved from the Internet: URL:http://proquest.safaribooksonline.com/0201844540> [retrieved on Mar. 28, 2008 and May 21, 2008]; Chapter 3 Section Databases and Other Back-End Resources; Chapter 13 Section Underutilization; 15 pages.
Kanodia, Vikram et al.; Multi-Class Latency-Bounded Web Services; 2000 Eighth International Workshop On Quality of Service; In Proceedings of IEEE/IFIP IWQoS 2000 (Cat. No. 00Ex400); IEEE Piscataway, NJ, USA, 2000; XP-002474136; ISBN: 0-7803-6266-7; pp. 231-239 (9 pages).
Mitchell, Mark et al.; Advanced Linux Programming; [Online] Jun. 11, 2001; XP-002474090; ISBN: 978-0-7357-1043-6; Retrieved from the Internet: URL:http://proquest.safaribooksonline.com/0735710430> [retrieved on Mar. 27, 2008]; Section 8.5; 4 pages.
Park, H.H. et al., On the Use of Genetic Algorithms in Database Client Clustering, Tools with Artificial Intelligence, 1999. Proceedings. International Conference on, Nov. 1999, pp. 339-342.

Cited By (53)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8386611B2 (en) 2003-10-29 2013-02-26 International Business Machines Corporation Information system, load control method, load control program and recording medium
US20090133031A1 (en) * 2003-10-29 2009-05-21 Masashi Inoue Information system, load control method, load control program and recording medium
US20060195579A1 (en) * 2005-02-28 2006-08-31 International Business Machines Corporation Method and system for managing server load to execute transactions of an application program on multiple servers
US7707581B2 (en) * 2005-02-28 2010-04-27 International Business Machines Corporation Method and system for managing server load to execute transactions of an application program on multiple servers
US20080082977A1 (en) * 2006-09-29 2008-04-03 Microsoft Corporation Automatic load and balancing for virtual machines to meet resource requirements
US8161475B2 (en) * 2006-09-29 2012-04-17 Microsoft Corporation Automatic load and balancing for virtual machines to meet resource requirements
US20080172671A1 (en) * 2007-01-11 2008-07-17 International Business Machines Corporation Method and system for efficient management of resource utilization data in on-demand computing
US20080195447A1 (en) * 2007-02-09 2008-08-14 Eric Bouillet System and method for capacity sizing for computer systems
US20090031019A1 (en) * 2007-07-27 2009-01-29 Burr Michael J Technique for Graphically Displaying Application Processing Time Distributions in Real-Time
US20090089418A1 (en) * 2007-10-01 2009-04-02 Ebay Inc. Method and system to detect a network deficiency
US8135824B2 (en) * 2007-10-01 2012-03-13 Ebay Inc. Method and system to detect a network deficiency
US8856196B2 (en) * 2008-07-22 2014-10-07 Toyota Jidosha Kabushiki Kaisha System and method for transferring tasks in a multi-core processor based on trial execution and core node
US20100262971A1 (en) * 2008-07-22 2010-10-14 Toyota Jidosha Kabushiki Kaisha Multi core system, vehicular electronic control unit, and task switching method
US8804940B2 (en) 2008-08-29 2014-08-12 8X8, Inc. Networked contact center
US10033869B2 (en) * 2008-08-29 2018-07-24 8X8, Inc. Methods and systems for information streaming to user interface
US11736618B1 (en) 2008-08-29 2023-08-22 8X8, Inc. Networked contact center user interface approach
US11539842B2 (en) 2008-08-29 2022-12-27 8X8, Inc. Methods and systems for information streaming to user interface
US11503157B2 (en) 2008-08-29 2022-11-15 8X8, Inc. Limiting contact in a networked contact center environment
US20100054439A1 (en) * 2008-08-29 2010-03-04 Contactual, Inc. Methods and systems for multilayer provisioning of networked contact centers
US20100057927A1 (en) * 2008-08-29 2010-03-04 Contactual, Inc. Methods and systems for information streaming to user interface
US8204206B2 (en) 2008-08-29 2012-06-19 8X8, Inc. Systems and methods for selection of a communication path
US8243913B2 (en) 2008-08-29 2012-08-14 8×8, Inc. Limiting contact in a networked contact center environment
US8275116B2 (en) 2008-08-29 2012-09-25 8X8, Inc. Networked contact center
US20100054451A1 (en) * 2008-08-29 2010-03-04 Contactual, Inc. Limiting contact in a networked contact center environment
US10868912B2 (en) 2008-08-29 2020-12-15 8X8, Inc. Methods and systems for information streaming to user interface
US8515833B2 (en) 2008-08-29 2013-08-20 8X8, Inc. Methods and systems for multilayer provisioning of networked contact centers
US20100054448A1 (en) * 2008-08-29 2010-03-04 Contactual, Inc. Systems and methods for selection of a communicatoin path
US10863031B1 (en) 2008-08-29 2020-12-08 8X8, Inc. Networked contact center user interface approach
US20100058234A1 (en) * 2008-08-29 2010-03-04 Contactual, Inc. Networked contact center user interface
US8855291B2 (en) 2008-08-29 2014-10-07 8X8, Inc. Limiting contact in a networked contact center environment
US10601990B2 (en) 2008-08-29 2020-03-24 8X8, Inc. Limiting contact in a networked contact center environment
US8972885B2 (en) 2008-08-29 2015-03-03 8X8, Inc. Networked contact center user interface
US10298767B1 (en) 2008-08-29 2019-05-21 8X8, Inc. Networked contact center user interface approach
US9049297B1 (en) 2008-08-29 2015-06-02 8X8, Inc. Networked contact center
US9225832B1 (en) 2008-08-29 2015-12-29 8X8, Inc. Networked contact center user interface
US9294625B2 (en) 2008-08-29 2016-03-22 8X8, Inc. Limiting contact in a networked contact center environment
US9307088B1 (en) 2008-08-29 2016-04-05 8×8, Inc. Networked contact center
US9438736B2 (en) 2008-08-29 2016-09-06 8X8, Inc. Limiting contact in a networked contact center environment
US9531879B1 (en) 2008-08-29 2016-12-27 8×8, Inc. Networked contact center user interface approach
US9838539B2 (en) 2008-08-29 2017-12-05 8X8, Inc. Limiting contact in a networked contact center environment
US9986091B2 (en) 2008-08-29 2018-05-29 8X8, Inc. Limiting contact in a networked contact center environment
US20100054450A1 (en) * 2008-08-29 2010-03-04 Contactual, Inc. Networked contact center
US20100268816A1 (en) * 2009-04-17 2010-10-21 Hitachi, Ltd. Performance monitoring system, bottleneck detection method and management server for virtual machine system
US8826274B2 (en) * 2010-06-11 2014-09-02 Hitachi, Ltd. Virtual machine system, networking device and monitoring method of virtual machine system
US20110307889A1 (en) * 2010-06-11 2011-12-15 Hitachi, Ltd. Virtual machine system, networking device and monitoring method of virtual machine system
US8468545B2 (en) 2010-08-18 2013-06-18 8X8, Inc. Interaction management
US8924386B2 (en) * 2010-09-01 2014-12-30 Fujitsu Limited Data distributing apparatus, data storing device, and recording medium
US20120054251A1 (en) * 2010-09-01 2012-03-01 Fujitsu Limited Data distributing apparatus, data storing device, and recording medium
US20150074262A1 (en) * 2013-09-12 2015-03-12 Vmware, Inc. Placement of virtual machines in a virtualized computing environment
US10348628B2 (en) * 2013-09-12 2019-07-09 Vmware, Inc. Placement of virtual machines in a virtualized computing environment
US10997051B2 (en) 2018-06-01 2021-05-04 TmaxSoft Co., Ltd. Server, method of controlling server, and computer program stored in computer readable medium therefor
US20210224263A1 (en) * 2019-02-08 2021-07-22 Intuit Inc. Graph database applications
US12086138B2 (en) * 2019-02-08 2024-09-10 Intuit Inc. Graph database applications

Also Published As

Publication number Publication date
US8386611B2 (en) 2013-02-26
CA2541576A1 (en) 2005-05-06
EP1679595A4 (en) 2008-06-04
CN1875348A (zh) 2006-12-06
IL174874A0 (en) 2006-08-20
BRPI0416101A (pt) 2007-01-02
EP1679595A1 (en) 2006-07-12
US20090133031A1 (en) 2009-05-21
CA2541576C (en) 2011-12-20
WO2005041038A1 (ja) 2005-05-06
JPWO2005041038A1 (ja) 2007-04-19
KR100866857B1 (ko) 2008-11-04
JP4205103B2 (ja) 2009-01-07
US20070157210A1 (en) 2007-07-05
KR20060079244A (ko) 2006-07-05
CN100465900C (zh) 2009-03-04
MXPA06004071A (es) 2006-06-27

Similar Documents

Publication Publication Date Title
US7480719B2 (en) Information system, load control method, load control program and recording medium
US7529903B2 (en) Systems and methods for memory migration
JP4920391B2 (ja) 計算機システムの管理方法、管理サーバ、計算機システム及びプログラム
JP4857818B2 (ja) ストレージ管理方法およびストレージ管理サーバ
US8250574B2 (en) Virtual machine management via use of table in which virtual machine information is registered on a time basis
US11016956B2 (en) Database management system with database hibernation and bursting
US7975268B2 (en) Grid computing system, management server, processing server, control method, control program and recording medium
US7702962B2 (en) Storage system and a method for dissolving fault of a storage system
US20080263128A1 (en) Information Processing System and Information Processing Device
US8176076B2 (en) Method and system for controlling accesses to a database
JP2014120097A (ja) 情報処理装置、プログラム、及び、情報処理方法
JP5552343B2 (ja) 管理装置、管理方法およびプログラム
US20120259588A1 (en) Method and apparatus for collecting performance data, and system for managing performance data
US6266697B1 (en) System automatically maintaining client under control of client, and a recording medium therefor
US6850957B2 (en) Information system and data access method
KR102187382B1 (ko) 클라우드 인프라 기반의 컨테이너 가상os 통합 모니터링 운영 방법
CN115756825A (zh) 一种中断负载均衡优化方法及装置
CN112073519B (zh) 操作请求的处理方法和装置
US20050144197A1 (en) System and method for highly available data processing in cluster system
CN121166739A (zh) 基于共享存储集群的事务状态获取方法及相关产品
JPH11259412A (ja) Ｉｏスループット向上方式
WO2016203613A1 (ja) 情報系システム及びデータベース管理方法

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INOUE, MASASHI;REEL/FRAME:017849/0202

Effective date: 20060420

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

REMI Maintenance fee reminder mailed
LAPS Lapse for failure to pay maintenance fees
STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20130120

AS Assignment

Owner name: KYNDRYL, INC., NEW YORK

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:057885/0644

Effective date: 20210930