Task management system

Abstract

To appropriately manage task execution.SOLUTION: A task management system comprises a processor and a memory. The memory stores consumption resource amount transition prediction of a resource consumed by a plurality of tasks and effective resource amount information for managing an effective resource amount indicating the total resource amount that can be provided from the resource. The processor, for the resource consumed by each of the plurality of tasks, compares consumption resource amount prediction obtained from the consumption resource amount transition prediction with a current consumption resource amount, determines that the effective resource amount of the resource is decreased when a predetermined condition including that the current consumption resource amount is smaller than the consumption resource amount prediction is satisfied, estimate a decrease amount of the effective resource amount on the basis of the difference between the current consumption resource amount and the consumption resource amount prediction, and determines an influence on task execution on the basis of the decrease amount.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to task management. [Background technology]

[0002] As background art in this technical field, there is Japanese Patent Application Laid-Open No. 2008-3736. This document discloses the following (see abstract): "At a computer center that provides users with computers for job execution, when a user wants to execute a job that exceeds the amount of computer resources available, the amount of computer resources becomes limited, and not all jobs can be executed, resulting in business delays. The object of this invention is to prevent business delays by preventing a shortage of computer resources." "A job execution prediction is made based on the job execution schedule applied for by the user and the job execution record, and a warning is issued if it is predicted that the job execution prediction will exceed the computer resources within the number of days it will take to add computer resources in the future." [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2008-3736 A Summary of the Invention [Problem to be solved by the invention]

[0004] By predicting the amount of resources that a task will consume before the task is executed, it is possible to allocate appropriate resources to the task. However, during the execution of a task or before the task is executed according to a planned schedule, the total amount of resources (available amount of resources) that can be given to the task (that can be consumed) and the amount of resources actually consumed by the task may change differently than expected. For example, disturbances such as maintenance processing other than the tasks on the system, performance degradation due to network delays or software failures, and degenerate operation due to hardware failures or software failures may affect the task-related resource amounts.

[0005] When a disturbance occurs, it is necessary to predict whether the target completion time of a task can be met due to resource shortages during task execution. In order to predict the completion time of a task, it is important to more accurately predict the decrease in the amount of available resources due to disturbances of unknown causes and the amount of resources consumed until the task is completed. [Means for solving the problem]

[0006] A representative example of the present invention is a task management system that manages multiple tasks executed by a target system, comprising a processor and a memory, wherein the memory stores a consumption resource amount trend prediction of resources consumed by the multiple tasks and effective resource amount information that manages an effective resource amount indicating the total resource amount that can be provided from the resources, and the processor compares the consumption resource amount prediction obtained from the consumption resource amount trend prediction with a current consumption resource amount for the resources consumed by each of the multiple tasks, and determines that the effective resource amount of the resource has decreased if a predetermined condition is satisfied including the current consumption resource amount being smaller than the consumption resource amount prediction, estimates the amount of decrease in the effective resource amount based on the difference between the current consumption resource amount and the consumption resource amount prediction, and determines the impact on task execution based on the amount of decrease. Effect of the Invention

[0007] One aspect of the present invention is the ability to more accurately predict the completion time of a task. [Brief description of the drawings]

[0008] [Figure 1] 1 illustrates an example of the configuration of a computer system according to an embodiment of the present specification. [Diagram 2] Examples of resources provided by the server include: [Diagram 3] 2 shows examples of resources provided by a storage system. [Figure 4] 1 shows an example of the configuration of a task schedule table. [Diagram 5] 13 shows an example of the configuration of a task table. [Figure 6] 1 shows an example of the current configuration of a system available resource amount table. [Figure 7] 13 shows an example of the configuration of a table of assumed available resource reduction amounts of a system. [Figure 8] 13 shows an example of the configuration of a table of assumed available resource reduction amounts for each task. [Figure 9] 1 shows an example of the current configuration of a system resource consumption table. [Figure 10] 13 shows an example of the configuration of a system resource consumption transition prediction table. [Figure 11] 13 shows an example of a configuration of a task-by-task resource consumption transition prediction table. [Figure 12] 13 shows an example of the configuration of a resource amount impact definition table by occurrence trigger. [Figure 13] 13 shows a flowchart of a process for updating the amount of resource consumed by the system. [Figure 14] 1 shows a flowchart of a task registration process. [Figure 15A] 1 shows a flowchart of a task execution process. [Figure 15B] 1 shows a flowchart of a task execution process. [Figure 16] 13 shows a flowchart of a process for calculating a forecast of changes in the amount of available resources in a system. [Figure 17A] 13 shows a flowchart of a process for detecting the occurrence of an unexpected disturbance and determining the degree of its influence. [Figure 17B] 13 shows a flowchart of a process for detecting the occurrence of an unexpected disturbance and determining the degree of its influence. [Figure 18] 13 shows a flowchart of a process for calculating an assumed reduction in available resources when a resource-consuming disturbance is detected. [Figure 19] 13 shows a flowchart of a process for calculating an assumed reduction in available resources when a non-resource-consuming disturbance is detected. [Figure 20] 13 shows a flowchart of a process for calculating an assumed effective resource reduction amount of a system. [Figure 21] 13 shows a flowchart of a process for calculating an amount of available resources for execution and determining the impact of a task. [Figure 22] 13 shows a flowchart of a resource shortage effect determination process for a task. [Diagram 23]1 shows a flowchart of a process for detecting an expected disturbance and determining its influence. [Figure 24A] An example of a task schedule image when a task is registered is shown below. [Figure 24B] 13 shows an example of a task schedule and an alert display image when a task fails to start. [Figure 24C] 13 shows an example of a display image of a task schedule and an alert when it is detected that a task target completion time has not been reached due to a disturbance. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] In the following, when necessary for convenience, the description will be divided into multiple sections or examples, but unless otherwise specified, they are not unrelated to each other, and one is related to the other as a partial or complete modification, detail, supplementary explanation, etc. Furthermore, in the following, when the number of elements, etc. (including the number, numerical value, amount, range, etc.) is mentioned, it is not limited to the specific number, and may be more or less than the specific number, unless otherwise specified or clearly limited in principle to a specific number, etc.

[0010] A computer system can be composed of one computer or multiple computers that can communicate with each other. A computer device, computer system, or group of computing resources includes one or more interface devices (including, for example, a communication device and an input / output device), one or more storage devices (including, for example, a memory (main memory) and an auxiliary storage device), and one or more processors.

[0011] When a function is realized by executing a program by a processor, the defined processing is performed using a storage device and / or an interface device, etc., as appropriate, and therefore the function may be considered to be at least a part of the processor. Processing described using a function as the subject may be processing performed by a processor or a system having the processor.

[0012] The program may be installed from a program source. The program source may be, for example, a program distribution computer or a computer-readable storage medium (for example, a computer-readable non-transitory storage medium). The description of each function is an example, and multiple functions may be combined into one function, or one function may be divided into multiple functions.

[0013] Task management according to an embodiment of the present specification will be described below. The management system executes a plurality of tasks using other devices and manages the plurality of tasks. Devices used to execute the tasks may include a processing server (also simply called a server), a storage system, a network, and the like. Note that there is no particular limitation on the configuration of the system to be managed.

[0014] Each device includes resources whose usage can be measured, such as a CPU (processor), memory (main memory), auxiliary storage device, network, or communication interface. The resources may include hardware resources and software resources. For example, the CPU and memory of a virtual machine may be included in the resources taken into account in task execution.

[0015] The management system constantly monitors the resource consumption of each part of each device. As described above, the device is, for example, a server or a storage system, and the part is, for example, a CPU or a memory. The resource amount of each part of each device managed by the management system is explained as follows.

[0016] The effective resource amount of each part is the maximum amount of resource for that part that the management system can assign to the task. The available resource amount is the amount of additional effective resource that the management system can assign to the task. The consumed resource amount is the amount of resource that the management system has assigned to the task. These three resource amounts satisfy the following relationship: Effective resource amount = Available resource amount + Consumed resource amount

[0017] Therefore, the amount of effective resources can be expressed by the amount of available resources and the amount of consumed resources, and the amount of available resources can be expressed by the amount of effective resources and the amount of consumed resources. A task consumes system resources to perform necessary processing. A task has constraints on its execution time. For example, there is a possible start time and a target completion time, and a task is required to be executed after the possible start time and to be completed by the target completion time. Multiple tasks can be executed simultaneously. The management system is required to schedule multiple tasks so as to avoid resource shortages for each task and to complete each task by its target completion time.

[0018] When the available amount of a certain resource becomes 0 and the amount of consumed resources required by any task is insufficient, that task is in a resource shortage state. When there is a resource shortage, the task execution time will be extended, which will cause the target completion time to be missed. Therefore, if a resource shortage is predicted, measures must be taken to deal with it.

[0019] A management system according to an embodiment of the present specification holds a schedule of tasks to be executed by managed systems and starts the tasks according to the schedule. A user or a management system determines an optimal schedule in advance, taking into account the resources of the system, to avoid resource shortages and to complete tasks within a target time.

[0020] During or before a task is executed, the amount of available resources may change differently from the prediction. Unpredicted changes in the amount of available resources also cause changes in the amount of available resources and the amount of consumed resources. A decrease in the amount of available resources may affect the target time for task completion, and is therefore called a disturbance to the execution of that task. Examples of disturbances include maintenance processing other than the task on the system (firmware updates, virus scans, etc.), performance degradation due to network delays or software failures, and degenerate operation due to hardware or software failures.

[0021] When a disturbance occurs and the amount of available resources decreases, that is, when task execution is started or continued in a state where the amount of available resources has decreased, a resource shortage may occur immediately. Alternatively, when the amount of resources consumed by a task increases, a resource shortage may occur. As a result of a resource shortage, a task may not be completed by the target completion time.

[0022] A management system according to an embodiment of the present specification estimates the occurrence of various disturbances, including disturbances that cannot be predicted in advance, and the resulting changes in the amount of available resources, and determines the impact of the changes on task execution. This reduces the possibility of tasks not being executed appropriately. For example, the management system calculates the possibility of a shortage of resources required by a task currently being executed or to be executed in the future, or the possibility of the target completion time being exceeded, based on the estimated changes in the amount of available resources. If the calculation reveals a resource shortage or a target completion time being exceeded, an alert of the problem is presented to the user.

[0023] A more specific configuration example of the present disclosure will be described below. FIG. 1 shows a configuration example of a computer system according to an embodiment of the present specification. The computer system includes a management server 10, a management client 30, and components of the managed system. The managed devices include a plurality of processing servers 40 (also simply called servers) and a plurality of storage systems 50. The management server 10 communicates with the management client 30 via a management LAN 37, and communicates with the managed devices 40, 50 via the management LAN 37. The types of these networks are arbitrary. The management server 10 and the management client 30 are a management system. The management client 30 may be omitted, and a plurality of management servers may execute the processes described below.

[0024] 1, one of the multiple servers is designated by the reference numeral 40 as an example, and one of the multiple storage systems is designated by the reference numeral 50 as an example. The server 40 executes an agent program 41. The agent program 41 provides information about the resources of the server 40 to the management server 10, and executes tasks in the server 40 or controls the execution of tasks in response to instructions from the management server 10.

[0025] The storage system 50 executes an agent program 51. The agent program 51 provides information on resources of the storage system 50 to the management server 10, and executes tasks in the storage system 50 or controls the execution of tasks in response to instructions from the management server 10.

[0026] The management server 10 grasps the status of resources of the server 40 and the storage system 50 via the agent programs 41, 51, and manages and controls tasks using the resources. The management server 10 includes a processor 11 and a memory 13 which is a main storage device. The processor 11 executes a group of programs 150 stored in the memory 13.

[0027] The management server 10 further includes a plurality of disks (also called storage drives) that are auxiliary storage devices, and a communication interface for communicating with other devices via a network, which are omitted in FIG.

[0028] The memory 13 is, for example, a DRAM which is a volatile storage device, and the disk is, for example, a solid state drive (SSD) or a hard disk drive (HDD) which is a non-volatile storage device. The number of each component of the management server 10 is not particularly limited, and other components such as an input device and an output device may be included. Examples of input devices are a mouse and a keyboard, and examples of output devices are a display device and a printer.

[0029] The programs (instruction codes) executed by the processor 11 and information used by the programs are stored, for example, on a disk and loaded into the memory 13. The processor 11 realizes predetermined functions by executing the programs stored in the memory 13 (by operating according to instructions in the programs). The processor 11 may include one or more processor units or processor cores.

[0030] The management client 30 is a device through which a user communicates with the management server 10, and transmits information to the management server 10 or receives information from the management server 10. The management server 10 presents information to the user via the management client 30. The management client 30 may have the configuration of a typical PC.

[0031] For example, the management client 30 may include a processor, a memory which is a main storage device, a disk which is a secondary storage device, a communication interface, an input device, and an output device, as described for the management server 10. Examples of the input device are a mouse and a keyboard, and examples of the output device are a display device and a printer.

[0032] The memory 13 of the management server 10 stores a management table group 130. The management table group 130 includes a task schedule table (TBL) 131, a task table 132, a current system available resource amount table 133, a current system consumed resource amount table 134, a system assumed available resource reduction amount table 135, a task-specific assumed available resource reduction amount table 136, a system consumed resource amount transition prediction table 137, a task-specific consumed resource amount transition prediction table 138, and an occurrence trigger-specific resource amount impact definition table 139. These will be described in detail later.

[0033] The memory 13 of the management server 10 stores a group of programs 150. The group of programs 150 includes a system consumption resource amount update program 151, a task registration program 152, a task execution program 153, an unanticipated disturbance detection and influence degree determination program 154, an anticipated disturbance detection and influence degree determination program 155, and a client interface program 156.

[0034] A system resource consumption update program 151 updates information on resource consumption in a managed system. A task registration program 152 registers task information in the management table group 130. A task execution program 153 commands the agent program of each device to execute a task based on the task information. Each device executes the command.

[0035] The unanticipated disturbance detection and influence degree judgment program 154 periodically monitors the execution state of each device and task, and detects disturbances and judges their influence. The unanticipated disturbance detection and influence degree judgment program 154 detects incompletion of a task before the target completion time of the task, and issues an alert to the management client 30 via the client interface program 156. In addition, the unanticipated disturbance detection and influence degree judgment program 154 presents the resource that is the source of the disturbance and the predicted completion time of the task to the management client 30 via the client interface program 156.

[0036] The expected disturbance detection / influence determination program 155 detects disturbances and determines their influence when a disturbance that is expected and defined in advance occurs. The expected disturbance detection / influence determination program 155 detects incompletion of a task before the target completion time of the task, and issues an alert to the management client 30 via the client interface program 156. Furthermore, the expected disturbance detection / influence determination program 155 presents the resource that is the source of the disturbance and the predicted completion time of the task to the management client 30 via the client interface program 156.

[0037] 2 and 3 show examples of resources contained in managed devices that are used to execute tasks. Servers and storage systems have resources such as CPUs and RAM that can be used to execute tasks. Examples of resources for each device are described below.

[0038] 2 shows an example of resources provided by the server 40. The types include a CPU, a RAM, a disk, and a network port. The disk is an auxiliary storage device, such as a HDD or SSD. The number of elements of each resource type may be one or more.

[0039] The CPU measures the time consumed per second in msec, with each core having an effective resource amount of 1000 msec. The time used for a specific process is the consumed resource amount. For RAM, the resource amount is its capacity. For disks, the resource amount is its capacity. Also, the resource amount is IOPS (number of responses per second). This makes it possible to convert response delays into resource amounts. For network ports, the resource amount is bandwidth. Also, the resource amount is IOPS (number of responses per second). This makes it possible to convert response delays into resource amounts. In this way, each part has one or more types of resource amount.

[0040] 3 shows an example of resources provided by the storage system 50. The types of resources include the same types of resources as the server 40, specifically, a CPU, RAM, disks, and network ports, as well as specific resources such as queues (not shown in FIG. 3).

[0041] Of the above available resources, the available resources of CPU and RAM can generally be fully used. On the other hand, the available resources of network bandwidth and IOPS may not be fully used due to various factors such as the state of the communication path and the communication destination. Such resources are also called resources with hidden reduction factors for available resources.

[0042] Fig. 4 shows an example of the configuration of the task schedule table 131. The task schedule table 131 manages the execution schedule of tasks, and is created and updated by the task registration program 152. In the example of the configuration of Fig. 4, the task schedule table 131 includes a task name column 311, a possible start time column 312, and a target completion time column 313.

[0043] The task name column 311 shows a name that identifies the task. The possible start time column 312 shows the time when execution of the task can start. The task can be executed on that day or later. The target completion time column 313 shows the target time for completing the task. The time is expressed as a date and a time within a day.

[0044] Fig. 5 shows an example of the configuration of the task table 132. The task table 132 manages a method for calculating the size of a task. The task table 132 is created and updated by the task registration program 152 in response to a user specification. In the example of the configuration of Fig. 5, the task table 132 includes a task name column 321. The task name column 321 indicates a name that identifies a task.

[0045] 6 shows an example of the configuration of the current system available resource amount table 133. The current system available resource amount table 133 manages the current available resource amount of each part of each device in the system. Information on the current available resource amount can be obtained from each device by the agent programs 41 and 51.

[0046] 6, the current system available resource amount table 133 includes a device name column 331, a part name column 332, a type column 333, and an available resource amount column 334. Each record indicates the available resource amount of one resource type of one part in one device. As described above, one or more resource types are defined for each part.

[0047] The device name column 331 indicates the name of the device that identifies the device, and the part name column 332 indicates the name of the part that identifies the part in each device. The type column 333 indicates the type of resource consumed by the part. The available resource amount column 334 indicates the current available resource amount.

[0048] 7 shows an example of the configuration of the system's assumed available resource reduction amount table 135. The system's assumed available resource reduction amount table 135 manages the estimated reduction amount of the available resource amount in the system due to disturbances. Disturbances that affect the system's resource amount include both disturbances that are anticipated (identifiable) and disturbances that are not anticipated (unidentifiable).

[0049] 7, the system's assumed available resource reduction amount table 135 includes a device name column 351, a part name column 352, a type column 353, and an available resource reduction amount column 354. The device name column 351 indicates the name of the device that identifies the device, and the part name column 352 indicates the name of the part that identifies the part in each device. The type column 353 indicates the type of resource consumed by the part. The available resource reduction amount column 354 indicates the amount of available resource reduction due to an estimated disturbance.

[0050] 8 shows an example of the configuration of the task-based assumed available resource reduction amount table 136. The task-based assumed available resource reduction amount table 136 manages the estimated reduction amount of the available resource amount in the system for each task due to disturbances. Disturbances that affect the resource amount of the system include both disturbances that are anticipated (identifiable) and disturbances that are not anticipated (unidentifiable).

[0051] 8, the task-specific assumed available resource reduction amount table 136 includes a task name 361, a device name column 362, a part name column 363, a type column 364, and an available resource reduction amount column 365. The task name 361 indicates a name that identifies a task. The device name column 362 indicates the name of a device that identifies a device, and the part name column 363 indicates the name of a part that identifies a part in each device. The type column 364 indicates the type of resource consumed by the part. The available resource reduction amount column 365 indicates the amount of available resource reduction for a task due to an estimated disturbance.

[0052] 9 shows an example of the configuration of the current system resource consumption table 134. The current system resource consumption table 134 manages the current resource consumption of each part of each device in the system. Information on the current resource consumption can be obtained from each device by the agent programs 41 and 51.

[0053] 9, current system resource consumption table 134 includes a device name column 341, a part name column 342, a type column 343, and a consumed resource column 344. Each record indicates the current resource consumption of one resource type of one part in one device. The device name column 341 indicates the name of the device that identifies the device, and the part name column 342 indicates the name of the part that identifies the part in each device. The type column 343 indicates the type of resource consumed by the part. The consumed resource column 344 indicates the current resource consumption.

[0054] 10 shows an example of the configuration of the system consumption resource amount trend prediction table 137. The system consumption resource amount trend prediction table 137 manages the prediction results of the trend of the consumed resource amount of each part of each device. The prediction of the trend of the consumed resource amount of each part of each device is executed by the task execution program 153.

[0055] 10, system resource consumption transition prediction table 137 includes a time column 371, a device name column 372, a part name column 373, a type column 374, and a consumed resource amount column 375. Each record shows the predicted resource consumption amount of one resource type of one part of one device in one time period. Each predicted resource consumption amount is the sum of the predicted resource consumption amounts of all tasks that use that resource.

[0056] The time column 371 indicates the start time of each time period in the time series. The length of the time period may be constant, for example. The time is expressed in days and the time. The device name column 372 indicates the name of the device that identifies the device, and the part name column 373 indicates the name of the part that identifies the part in each device. The type column 374 indicates the type of resource consumed by the part. The consumed resource amount column 375 indicates the predicted amount of resource consumed.

[0057] 11 shows an example of the configuration of per-task resource consumption amount transition prediction table 138. Per-task resource consumption amount transition prediction table 138 manages the prediction results of the transition of the resource consumption amount of each part of each device for each task. The prediction of the transition of the resource consumption amount of each part of each device for each task is executed by task execution program 153.

[0058] 11, task-specific resource consumption transition prediction table 138 includes a task name column 381, a time column 382, ​​a device name column 383, a part name column 384, a type column 385, and a consumed resource amount column 386. Each record indicates the predicted resource consumption amount of one resource type, of one part in one device, during one time period, by a specified task.

[0059] The time column 382 indicates the start time of each time period in the time series. The length of the time period may be constant, for example. The device name column 383 indicates the name of the device that identifies the device, and the part name column 384 indicates the name of the part that identifies the part in each device. The type column 385 indicates the type of resource consumed by the part. The resource consumption amount column 386 indicates the predicted resource consumption amount.

[0060] Fig. 12 shows an example of the configuration of the resource quantity impact definition table 139 by occurrence trigger. The resource quantity impact definition table 139 by occurrence trigger defines identifiable (assumed) disturbances and the impact of these disturbances on resources. In the configuration example of Fig. 12, the resource quantity impact definition table 139 by occurrence trigger includes an occurrence trigger column 391 and an impact on resources column 392. The occurrence trigger column 391 indicates the occurrence trigger of an identifiable disturbance. The impact on resources column 392 indicates the impact on resources by the disturbance for each occurrence trigger.

[0061] 13 shows a flowchart of a system consumption resource amount update process. This process updates information on the current consumption resource amount in the system, for example, periodically. Specifically, the system consumption resource amount update program 151 acquires the current consumption resource amount of the system from each device in the system (S11). This information can be acquired from the agent program of each device. The system consumption resource amount update program 151 updates the current system consumption resource amount table 134 with the acquired information (S12).

[0062] 14 shows a flowchart of the task registration process. The task registration process generates a task schedule in accordance with user input. The task registration program 152 receives information about the task input by the user via the management client 30 (S21). The task registration program 152 updates the task schedule table 131 and the task table 132 in accordance with the user input (S22). Note that the information about the task provided by the user may include information different from the information stored in the tables 131 and 132.

[0063] The task schedule may be specified by the user. The user can avoid resource shortages and complete tasks within a target time by determining an optimal schedule that takes into account the resources of the system in advance. Alternatively, the task registration program 152 may generate a task schedule from information about tasks provided by the user. The task registration program 152 displays the task schedule, including the registered tasks, on the display device of the management client 30 (S23).

[0064] 15A and 15B show flowcharts of the task execution process. The management server 10 starts a task according to the task schedule shown in the task schedule table 131. When starting a new task, one or more tasks may already be running, or no tasks may be running.

[0065] First, the task execution program 153 obtains information required to execute a new task from the management table group 130 (S31). Specifically, the task schedule of the task to be started, task information of the task to be started, the current system available resource amount, the system's assumed available resource reduction amount, and the predicted transition of the system resource consumption amount are obtained. These can be obtained from the task schedule table 131, the task table 132, the current system available resource amount table 133, the system's assumed available resource reduction amount table 135, and the predicted transition of the system resource consumption amount table 137.

[0066] Next, the task execution program 153 executes a task consumption resource amount transition prediction process and obtains the result (S33). The task consumption resource amount transition prediction process can be implemented by a general method. For example, the task execution program 153 predicts the transition of the consumption resource amount of an executing task based on information about the executing task and the execution history of various tasks in the past. Information about the executing task and the past execution history may be provided by the user or may be stored in advance in a management table group.

[0067] Next, the task execution program 153 executes a prediction calculation of the transition of the available resource amount of the system, and obtains the result (S34). The transition of the available resource amount can be predicted based on the effective resource amount of the system and the transition of the resource amount consumed by the task.

[0068] 16 is a flowchart of the system available resource amount transition prediction calculation process. The task execution program 153 acquires necessary information from the management tables (S61). Specifically, information on the current system available resource amount, the system's assumed available resource reduction amount, and the system consumption resource amount transition prediction is acquired. These can be acquired from the current system available resource amount table 133, the system's assumed available resource reduction amount table 135, and the system consumption resource amount transition prediction table 137.

[0069] Next, the task execution program 153 calculates the effective available resource amount of the system (S62). The effective available resource amount can be calculated according to the following formula. Effective amount of available resources of the system = Current system available resources - system assumed available resources reduction

[0070] Next, the task execution program 153 calculates a predicted transition of the amount of available resources in the system (S63). The predicted transition of the amount of available resources in the system can be calculated according to the following formula. Prediction of system available resource trends = Effective amount of available resources of the system - Prediction of the amount of resources consumed by the system

[0071] Returning to Figure 15A, the process flow proceeds to the step of Figure 15B via connector A. Referring to Figure 15B, the task execution program 153 executes steps S35 to S38 for each resource of the system.

[0072] In step S35, the task execution program 153 compares the amount of resource consumed by the execution task with the amount of available resource in the system for the selected resource at each time during the period for which the transition of the amount of resource is predicted. If the amount of resource consumed by the execution task is equal to or less than the amount of available resource during the entire period (S36: YES), the loop for the selected resource ends.

[0073] If at any point in time the resource consumption of the executing task is greater than the available resource amount (S36: NO), the task execution program 153 extends the execution time of the task by the same area (time x resource amount) so that the task consumption resource amount = the available resource amount, and updates the task consumption resource amount transition prediction (S37). In other words, the value of (task consumption resource amount / system available resource amount) is multiplied by the remaining time until the target completion time of the task to extend it. The longest extension result represents the task predicted completion time.

[0074] Next, the task execution program 153 determines whether the task will be completed by the target completion time. That is, it determines whether the predicted completion time of the task is before the target completion time (S38). If the predicted completion time is after the target completion time (S38: NO), the task execution program 153 uses the client interface program 156 to send an alert to the management client 30 (S39), and displays a failure to start task execution on the management client 30 (S40).

[0075] If the task consumption amount for all resources in the entire period is equal to or less than the available resource amount, the flow leaves the loop and proceeds to step S41. In step S41, the task execution program 153 adds the task consumption amount transition prediction to the system consumption amount transition prediction.

[0076] Next, the task execution program 153 updates the system resource consumption amount transition prediction table 137 (S42). Furthermore, the task execution program 153 registers the task consumption resource amount transition prediction in the task-by-task resource consumption amount transition prediction table 138 (S43). After that, the task execution program 153 instructs the agent program to start execution of the task (S44).

[0077] As described above, by performing a task consumption resource amount trend prediction based on the execution effective resource amount corrected by the effective resource amount based on information on the system's assumed effective resource reduction amount, it is possible to more accurately predict whether a pre-start task can be completed by the target completion time.

[0078] Next, a process for detecting an unanticipated disturbance will be described. The occurrence of a disturbance may affect the amount of resources in the system. In addition to identifiable types of disturbances that are anticipated in advance, there are also unanticipated and unidentifiable types of disturbances that may affect the system resources. The following describes a process for detecting the occurrence of an unanticipated disturbance and determining its impact on the system resources and task schedule.

[0079] 17A and 17B show a flowchart of the process of detecting the occurrence of an unexpected disturbance and determining the degree of influence. This process is executed, for example, periodically. The unexpected disturbance detection / influence degree determination program 154 acquires necessary information from the management table group 130 (S71). Specifically, information on the predicted transition of the system resource consumption amount and the predicted transition of the resource consumption amount for each task is acquired. These can be acquired from the predicted transition of the system resource consumption amount table 137 and the predicted transition of the resource consumption amount for each task table 138.

[0080] Next, the unanticipated disturbance detection / influence degree determination program 154 acquires the amount of resources currently consumed by tasks in the system from the system via the agent programs 41, 51 (S72).

[0081] Next, the unanticipated disturbance detection / influence degree determination program 154 executes steps S73 to S77 for each task currently being executed.

[0082] First, the unanticipated disturbance detection / impact degree determination program 154 acquires the current resource consumption amount prediction from the resource consumption amount transition prediction of the selected task (S73). Next, the unanticipated disturbance detection / impact degree determination program 154 compares the current resource consumption amount of the task acquired from the system with the current resource consumption amount prediction of the task (S74).

[0083] The unanticipated disturbance detection and influence degree determination program 154 calculates the assumed reduction amount of available resources when a resource consuming disturbance is detected based on the comparison result (S75). More specifically, the following process is executed.

[0084] 18 shows a flowchart of the calculation process (S75) of the deemed reduction in available resource amount when a resource consumption type disturbance is detected. The unanticipated disturbance detection / influence degree determination program 154 executes steps S91 to S95 for each resource of the system. The unanticipated disturbance detection / influence degree determination program 154 calculates the deemed reduction in available resource amount for resources that satisfy predetermined conditions.

[0085] The unanticipated disturbance detection and influence degree determination program 154 compares the current resource consumption amount of the resource of the task with the current resource consumption amount prediction of the resource of the task (S91). If the current resource consumption amount is equal to or greater than the current resource consumption amount prediction (S91: NO), the next resource is selected and step S91 is executed.

[0086] If the current resource consumption amount is less than the current resource consumption amount prediction (S91: YES), the unanticipated disturbance detection / influence degree determination program 154 compares the current resource consumption amount of the resource in question in the system with the effective resource amount of that resource. Here, it is determined whether the difference between the current resource consumption amount of the resource in question in the system and the effective resource amount of that resource (available resource amount) is equal to or less than a predetermined threshold and substantially matches (the available resource amount is substantially zero) (S92). The threshold may be 0 or a number greater than that.

[0087] If the value obtained by subtracting the current resource consumption amount of the resource from the available resource amount of the resource exceeds the threshold value (S92: NO), the next resource is selected and step S91 is executed. If the current resource consumption amount of the resource and the available resource amount of the resource substantially match (S92: YES), the unanticipated disturbance detection and influence degree determination program 154 determines that an assumed decrease in the available resource amount has been detected (S93). In other words, it is determined that some disturbance has occurred and that a decrease in the available resource amount that is not reflected in the management information has occurred.

[0088] Next, the unanticipated disturbance detection and influence degree judgment program 154 calculates the deemed reduction in the available resource amount of the task and the resource (S94). The deemed reduction in the available resource amount can be calculated by the following formula. Effective resource reduction amount = Estimated resource consumption amount - Current resource consumption amount The predicted amount of consumed resource and the current amount of consumed resource are both values ​​of the task and the resource.

[0089] Furthermore, the unanticipated disturbance detection and influence degree determination program 154 registers (updates) the deemed effective resource amount reduction amount of the task and the resource in the task-specific deemed effective resource reduction amount table 136 .

[0090] Returning to FIG. 17A, the unanticipated disturbance detection and impact degree determination program 154 determines in step S75 whether a deemed decrease in the amount of available resources has been detected (S76). If a deemed decrease in the amount of available resources has been detected (S76: YES), this loop for the task is terminated, and the next task is selected. If a deemed decrease in the amount of available resources has not been detected (S76: NO), the unanticipated disturbance detection and impact degree determination program 154 executes a calculation of the amount of deemed decrease in available resources when a non-resource consuming disturbance is detected (S77). More specifically, the following process is executed.

[0091] FIG. 19 shows a flowchart of the calculation process (S77) of the deemed reduction in available resource when a non-resource-consuming disturbance is detected. The unanticipated disturbance detection / impact degree determination program 154 executes steps S101 to S103 for each resource in the system that has a hidden effective resource reduction factor. The types of resources that have a hidden effective resource reduction factor are set in advance. A resource that has a hidden effective resource reduction factor is a resource whose effective resource amount cannot be fully used due to various factors such as the communication path and the state of the communication destination. The unanticipated disturbance detection / impact degree determination program 154 calculates the deemed reduction in available resource amount for resources that satisfy predetermined conditions.

[0092] The unanticipated disturbance detection and influence degree determination program 154 compares the current resource consumption amount of the task and the resource with the current resource consumption amount prediction of the task and the resource (S101). If the current resource consumption amount is equal to or greater than the resource consumption amount prediction (S101: NO), the next resource having the hidden effective resource reduction factor is selected, and step S101 is executed.

[0093] If the current resource consumption amount is less than the predicted resource consumption amount (S101: YES), the unanticipated disturbance detection and influence degree determination program 154 calculates the resource decrease rate (S102). The resource decrease rate can be calculated by the following formula. Resource reduction rate = current resource consumption / predicted resource consumption

[0094] Next, if the calculated resource decrease rate is the minimum resource decrease rate of the task, the unanticipated disturbance detection and influence degree determination program 154 records the resource decrease rate and the resource in question in the management information (S103).

[0095] When steps S101 to S103 are executed for all resources having the hidden effective resource reduction factor, the unanticipated disturbance detection and influence degree determination program 154 calculates the assumed reduction amount of the effective resource amount of the task (S104). Specifically, the unanticipated disturbance detection and influence degree determination program 154 executes the following calculation formula for the resource having the hidden effective resource reduction factor that has the smallest resource reduction rate of the task. Effective resource reduction amount = Estimated resource consumption amount - Current resource consumption amount

[0096] Next, the unanticipated disturbance detection and influence degree determination program 154 registers (updates) the assumed effective resource amount reduction amount of the task and the resource in the task-specific assumed effective resource reduction amount table 136 .

[0097] Returning to Fig. 17A, when steps S73 to S77 have been executed for all tasks currently being executed, the process flow proceeds to the step in Fig. 17B via connector B. Referring to Fig. 17B, the unanticipated disturbance detection and influence degree determination program 154 calculates the amount of reduction in the system's deemed effective resources (S78). More specifically, the following process is executed.

[0098] 20 shows a flowchart of the calculation process (S78) of the deemed effective resource reduction amount of the system. The unanticipated disturbance detection and influence degree determination program 154 executes steps S111 to S113 for each of the resources of the system.

[0099] First, the unanticipated disturbance detection and influence degree determination program 154 acquires necessary information from the management table group 130 (S111). Specifically, information on the task-specific deemed available resource reduction amount of the available resource is acquired from the task-specific deemed available resource reduction amount table 136.

[0100] Next, the unanticipated disturbance detection and influence degree determination program 154 sums up the assumed available resource reduction amount for each task for the resource for all tasks (S112). Next, the unanticipated disturbance detection and influence degree determination program 154 updates the system's assumed available resource reduction amount table 136 for the available resource with the summed value (S113).

[0101] Returning to Fig. 17B, the unanticipated disturbance detection / influence degree determination program 154 executes calculation of the amount of available resources for execution and judgment of the influence degree of the task (S79). More specifically, the following processing is executed. Fig. 21 shows a flowchart of the calculation of the amount of available resources for execution and judgment of the influence degree of the task (S79).

[0102] First, the unanticipated disturbance detection / influence degree determination program 154 acquires necessary information from the management table group 130 (S121). Specifically, information on the amount of available resources of the system, the amount of assumed available resources reduced by the system, and the predicted trend in the amount of resources consumed by the system is acquired. These can be acquired from the current system available resource amount table 133, the assumed available resource reduction amount table 135, and the predicted trend in the amount of resources consumed by the system table 137.

[0103] Next, the unanticipated disturbance detection and influence degree determination program 154 calculates the effective available resource amount for each of the resources of the system (S122). The effective available resource amount can be calculated according to the following formula. Effective amount of available resources of the system = Amount of available resources of the system - Amount of reduction in the assumed available resources of the system

[0104] Next, the unanticipated disturbance detection and influence degree determination program 154 compares the resource amounts of the respective resources of the system (S123). Specifically, the predicted transition of the resource consumption amount of the system is compared with the effective available resource amount of the system.

[0105] If the condition of predicted resource consumption amount transition≦effective resource amount of the system is satisfied for all resources over the entire period (S124: YES), this process flow ends. If this condition is not satisfied (S124: NO), the unanticipated disturbance detection / influence degree determination program 154 determines the influence of resource shortage on the task (S125). Specifically, the following process is executed.

[0106] FIG. 22 shows a flowchart of the resource shortage impact determination process for a task (S125). The process shown in FIG. 22 is executed for each resource of the system. First, the unanticipated disturbance detection / impact degree determination program 154 acquires necessary information from the management table group 130 (S131). Specifically, information on the predicted trend in the resource consumption amount for each task is acquired from the predicted trend in the resource consumption amount for each task table 138. Note that information on the system's available resource amount, the system's assumed available resource reduction amount, and the predicted trend in the resource consumption amount for the system have already been acquired.

[0107] Next, the unanticipated disturbance detection and influence degree judgment program 154 calculates the system resource shortage amount for each point in time during the shortage period, and further calculates the task resource shortage amount at each point in time (S132). The shortage period is a period during which the predicted transition of the system's resource consumption amount is greater than the system's effective resource amount. The task resource shortage amount can be calculated according to the following formula. Task resource shortage = (Predicted change in system resource consumption - Effective system resource usage) / Number of running tasks

[0108] Next, the unanticipated disturbance detection / impact degree determination program 154 executes steps S133 and S134 for each currently executed task. First, for each point in time during the shortage period, the unanticipated disturbance detection / impact degree determination program 154 subtracts the task resource shortage amount at each point in time from the task consumption resource amount transition prediction. When the task consumption resource amount becomes that resource amount, the task execution time is extended by the same area (time x resource amount) and the task consumption resource amount transition prediction is updated (S133). In other words, the value of (task consumption resource amount / system available resource amount) is multiplied by the remaining time until the target completion time of the task to extend it. The longest extension result among these represents the task predicted completion time.

[0109] Next, the unanticipated disturbance detection / influence degree determination program 154 updates the task-by-task resource consumption transition prediction table 138 with the updated task-by-task resource consumption transition prediction (S134). When steps S133 and S134 have been executed for all currently executing tasks, the process flow proceeds to step S135.

[0110] In step S135, the unanticipated disturbance detection / influence degree determination program 154 adds up the task-specific resource consumption transition predictions of all currently executing tasks, sets the sum as the system resource consumption transition prediction, and updates the system resource consumption transition prediction table 137 with the sum (S135).

[0111] Returning to Fig. 17B, the unanticipated disturbance detection and impact degree determination program 154 compares the predicted task completion time with the task target completion time for all currently executing tasks (S80). If the predicted completion times of all currently executing tasks are before the target completion times (S80: YES), this processing flow ends. If the predicted completion time of any task is after the target completion time, the unanticipated disturbance detection and impact degree determination program 154 uses the client interface program 156 to send an alert to the management client 30 (S81), and presents the resource that is the disturbance source and the predicted completion time of the task in the management client 30 (S82).

[0112] Next, a process for detecting the occurrence of a disturbance that is anticipated in advance and determining its impact on system resources and task schedules will be described. In addition to the process for unanticipated disturbances, the management server 10 also detects anticipated disturbances and determines their impact. This allows for more appropriate task schedule management. Note that the process for anticipated disturbances described below may be omitted.

[0113] As described above, one embodiment of the present specification determines the impact of unanticipated disturbances on task execution. The management server 10 monitors the amount of resource consumption consumed by each task, and if the current amount of resource consumption of each task is less than the predicted amount of resource consumption and there is essentially no available resource remaining, it determines that a disturbance causing a resource shortage has occurred. In addition, the difference between the predicted amount of resource consumption and the current amount of resource consumption is interpreted as the amount of reduction in the effective amount of resource (the amount of available resource) and calculated (S75).

[0114] Furthermore, the management server 10 determines that an implicit disturbance has occurred for each task when the current resource consumption amount is less than the predicted resource consumption amount and the available resource amount is substantially zero. A resource that may have an implicit disturbance is a resource that has a hidden effective resource decrease factor. The management server 10 determines that the resource with the lowest decrease rate of the resource consumption amount is the cause, and interprets and calculates the difference in the resource consumption amount as the decrease amount of the effective resource amount (available resource amount) (S77).

[0115] Based on the estimated value of the change in the amount of available resources due to disturbances, the management server 10 calculates the possibility of a shortage in the amount of consumed resources required by a task currently being executed or to be executed in the future, and the possibility of the task completion exceeding the target completion time. By considering the above two types of disturbances, it is possible to more appropriately estimate the impact of disturbances on task execution. Note that only one of them may be considered.

[0116] 23 shows a flowchart of the process of detecting an expected disturbance and judging the degree of its influence. This process is started by a pre-specified occurrence trigger, which may include a specific fault such as a network delay, a software fault, a hardware fault, or a specific process such as a maintenance process or a degenerate operation. The occurrence trigger and its influence on resources are defined in a resource amount influence definition table 139 by occurrence trigger.

[0117] First, depending on the occurrence trigger, the expected disturbance detection and influence degree determination program 155 acquires information required for the following processing from the management table group 130 (S141). Specifically, the current system resource consumption amount, the predicted trend of the system resource consumption amount, the predicted trend of the resource consumption amount for each task, and the resource amount impact definition by occurrence trigger are acquired. These can be acquired from the current system resource consumption amount table 134, the predicted trend of the system resource consumption amount table 137, the predicted trend of the resource consumption amount for each task table 138, and the resource amount impact definition table by occurrence trigger 139.

[0118] Next, the expected disturbance detection / impact degree determination program 155 refers to the occurrence trigger-specific resource amount impact definition table 139 to determine the impact of the predefined occurrence trigger on the system resource amount (S142). If the impact is on the available resource amount (S142: available resource amount), the expected disturbance detection / impact degree determination program 155 acquires necessary information from the management table group 130 (S143). Specifically, information on the system's current available resource amount is acquired from the current system available resource amount table 133.

[0119] Next, the expected disturbance detection and impact determination program 155 updates the current available resource amount of the system in accordance with the impact defined in the resource amount impact definition table by occurrence trigger 139, and reflects the update in the current system consumption resource amount table 134.

[0120] In step S142, if the influence is on the amount of consumed resources (S142: amount of consumed resources), the expected disturbance detection / impact degree determination program 155 registers the expected transition of the amount of consumed resources influenced by the disturbance as a task in the task-by-task consumed resources transition prediction table 138 (S145). Furthermore, the expected disturbance detection / impact degree determination program 155 adds up the task-by-task consumed resources transition predictions of all currently executing tasks to obtain the system consumed resources transition prediction table 137 accordingly (S146).

[0121] Next, the expected disturbance detection and impact determination program 155 calculates the assumed effective resource decrease amount of the system (S147). The assumed effective resource decrease amount of the system is the effective resource amount before and after the update. The explanation for unanticipated disturbance (S78) can be applied to step S147. The current effective resource amount of the system and the current Furthermore, the expected disturbance detection and impact determination program 155 executes calculation of the effective effective resource amount and impact determination of the task (S148). The explanation for unanticipated disturbance (S79) can be applied to step S148.

[0122] Next, the expected disturbance detection and influence degree determination program 155 determines whether the predicted task completion time is before the task target completion time for all currently executed tasks (S149). If all tasks are predicted to be completed by the task target completion time (S149: YES), this processing flow ends.

[0123] If any task is predicted to be completed after the target completion time (S149: NO), the expected disturbance detection and impact determination program 155 uses the client interface program 156 to send an alert to the management client 30 (S150), and presents the resource that is the source of the disturbance and the predicted completion time of the task on the management client 30 (S151).

[0124] As described above, one embodiment of the present specification predicts a change in the amount of available resources in response to the occurrence of a disturbance that is expected in advance. The impact of a disturbance on the amount of available resources and the amount of consumed resources is defined in advance in the resource amount impact definition table 139 by occurrence trigger. The occurrence of a defined disturbance is monitored, and when the occurrence of a disturbance is detected, the current amount of available resources and the amount of consumed resources are recalculated. This enables more accurate prediction of a specific disturbance.

[0125] An example of information transmitted from the management server 10 and displayed on the management client 30 will be described below. As described above, the management server 10 registers a task schedule according to user input from the management client 30. Thereafter, when the management server 10 determines that the task will not be completed by the target completion time due to a disturbance after the task is executed, it transmits an alert to the management client 30. This makes it possible to more appropriately support task management by the user.

[0126] Fig. 24A shows an example of a task schedule display screen when a task is registered. Each band indicates the possible start time and the target completion time for each task. Fig. 24B shows an example of a task schedule and alert display image when a task fails to start. In the example of Fig. 24B, a task schedule 511 and a resource amount transition forecast 512 for CPU1 of server 1 are displayed. It has been determined that task 4 will not be completed by the target completion time.

[0127] Task schedule 511 shows the estimated start and completion times of each task using bands. In addition, two bands are displayed for task 4, showing the target completion time and the delayed predicted completion time, respectively.

[0128] When task 4 is clicked (selected) in the task schedule 511, a resource amount trend forecast 512 of the CPU 1 of the server 1 is displayed. The resource amount trend forecast 512 of the CPU 1 of the server 1 shows a trend forecast of the amount of resources consumed by the CPU 1 of the server 1 by tasks 4, 5, and 6. Also shown are the available resources, the executed available resources, the target completion time of task 4, and the delayed predicted completion time of task 4.

[0129] Fig. 24C shows an example of a display image of a task schedule and an alert when it is detected that the task target completion time has not been reached due to a disturbance. In the example of Fig. 24C, a task schedule 521 and a resource amount transition forecast 522 of network port 1 of server 1 are displayed. It is determined that task 3 will not be completed by the target completion time.

[0130] Task schedule 521 shows the estimated start and completion times of each task using bands. In addition, two bands are displayed for task 3, showing the target completion time and the delayed predicted completion time, respectively.

[0131] When task 3 is clicked (selected) in task schedule 521, resource amount trend forecast 522 of network port 1 of server 1 is displayed. Resource amount trend forecast 522 of network port 1 of server 1 shows a trend forecast of the amount of resources consumed by tasks 1, 2, and 3 on network port 1 of server 1. Also shown are available resources, active available resources, the target completion time of task 3, and the delayed predicted completion time of task 3.

[0132] The present invention is not limited to the above-mentioned embodiment, but includes various modified examples. For example, the above-mentioned embodiment has been described in detail to clearly explain the present invention, and is not necessarily limited to those including all of the configurations described. It is also possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. It is also possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.

[0133] In addition, the above-mentioned configurations, functions, processing units, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. In addition, the above-mentioned configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as the program, table, file, etc. that realizes each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card or SD card.

[0134] In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. In reality, it can be considered that almost all components are connected to each other. [Explanation of symbols]

[0135] 10 Management Server 11 Processors 13. Memory 30 Management Client 40 Processing Server 50 Storage Systems

Claims

1. A task management system for managing multiple tasks executed by a target system, comprising: A processor; A memory, The memory includes: A prediction of a change in the amount of consumed resources of the resources consumed by the plurality of tasks; effective resource amount information for managing an effective resource amount indicating a total resource amount that can be provided from the resource; The processor Regarding the resources consumed by each task of the plurality of tasks, A consumption resource amount prediction obtained from the consumption resource amount transition prediction is compared with a current consumption resource amount; determining that an effective resource amount of the resource is decreasing when a predetermined condition is satisfied, the predetermined condition including that the current resource consumption amount is smaller than the predicted resource consumption amount; A reduction amount of the available resource amount is estimated based on a difference between the current consumed resource amount and the predicted consumed resource amount; The task management system determines an impact on task execution based on the amount of decrease.

2. The task management system according to claim 1, A task management system, wherein the specified condition further includes a difference between an available resource amount of the resource and a currently consumed resource amount of the resource being less than a threshold value.

3. The task management system according to claim 1, A task management system, wherein the specified conditions include the resource being a pre-designated resource and being a resource consumed by the task that has the smallest ratio of the current resource consumption amount to the predicted resource consumption amount.

4. The task management system according to claim 1, A task management system, wherein the resources consumed by the multiple tasks include a bandwidth of a network port.

5. The task management system according to claim 1, The memory further stores disturbance definition information that defines an effect of a disturbance on a resource in the target system; The processor, Detecting a disturbance indicated by the disturbance definition information; determining a change in the available resource amount due to the detected disturbance based on the disturbance definition information; A task management system that determines an effect on a predicted completion time of an ongoing task based on the change in the amount of available resources.

6. The task management system according to claim 1, The processor calculates the amount of reduction in the effective resource amount of the resource from a sum of the amount of reduction in the effective resource amount of the multiple tasks, The task management system determines whether or not there is a task whose predicted completion time will exceed a target completion time based on the amount of decrease in the effective resource amount of the resource and the predicted transition of the consumed resource amount.

7. The task management system according to claim 1, The processor, A task management system that presents an alert to a user when there is a task whose predicted completion time exceeds a target completion time.

8. 1. A method for a management system to manage multiple tasks performed by a target system, comprising: The management system includes: A prediction of a change in the amount of consumed resources of the resources consumed by the plurality of tasks; effective resource amount information for managing an effective resource amount indicating a total resource amount that can be provided from the resource; The method further comprises the steps of: Regarding the resources consumed by each task of the plurality of tasks, A consumption resource amount prediction obtained from the consumption resource amount transition prediction is compared with a current consumption resource amount; determining that an effective resource amount of the resource is decreasing when a predetermined condition is satisfied, the predetermined condition including that the current resource consumption amount is smaller than the predicted resource consumption amount; determining an amount of reduction in the amount of available resources based on a difference between the current amount of consumed resources and the predicted amount of consumed resources; determining an impact on task performance based on the amount of decrease.

Images