Task management method, device and computer program product
By acquiring the backup task group executed in parallel and its predicted backup speed, the problem of data backup time prediction in the prior art is solved, and more accurate time prediction and more efficient backup task management are achieved.
Patent Information
- Application Number
- CN201910990434.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-10-17
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2039-10-17
AI Technical Summary
The prior art lacks time-lapse in predicting data backup, especially as the amount of data increases, traditional solutions need to traverse a large amount of historical data, resulting in the prediction process taking too long and cannot meet the timeliness requirements of backup operations.
By obtaining the execution plan associated with the target backup task, the backup task group executed in parallel and its predicted backup speed are determined, and the time required for the target backup task is calculated based on this information.
It realizes more accurately predicting the time required for backup tasks, improves the time prediction efficiency of backup tasks, and supports users to better plan their work.
Smart Images

Figure CN112685224B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate to the field of computers, and more particularly, to a method, device, and computer program product for task management. Background Art
[0002] In recent years, with the development of computer technology, people will generate a large amount of electronic data every day. Users or service providers usually ensure the security of data by backing up data to prevent some unexpected situations. Usually, the data that needs to be backed up may be large in scale, and people expect to be able to predict the time required to perform data backup so as to better schedule tasks. Therefore, how to efficiently predict the time required for data backup has become a focus of attention at present. Summary of the invention
[0003] Embodiments of the present disclosure provide a solution for task management.
[0004] According to a first aspect of the present disclosure, a method for task management is provided. The method includes: obtaining an execution plan associated with a plurality of backup tasks including a target backup task, the execution plan at least indicating the backup data volume and start time of the plurality of backup tasks; determining a first group of backup tasks to be executed in parallel at the start time of the target backup task based on the execution plan; determining a predicted backup speed of executing the first group of backup tasks in parallel at the start time of the target backup task; and determining a time required to execute the target backup task based at least on the predicted backup speed and the backup data volume of the target backup task.
[0005] According to a second aspect of the present disclosure, a device for task management is proposed. The device includes: at least one processing unit; at least one memory, the at least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit, the instructions, when executed by the at least one processing unit, make the device perform an action, the action including: obtaining an execution plan associated with multiple backup tasks including a target backup task, the execution plan at least indicating the backup data volume and start time of the multiple backup tasks; based on the execution plan, determining a first group of backup tasks to be executed in parallel at the start time of the target backup task; determining a predicted backup speed for executing the first group of backup tasks in parallel at the start time of the target backup task; and determining the time required to execute the target backup task based at least on the predicted backup speed and the backup data volume of the target backup task.
[0006] In a third aspect of the present disclosure, a computer program product is provided. The computer program product is stored in a non-transitory computer storage medium and includes machine executable instructions, which, when executed in a device, cause the device to perform any step of the method described in the first aspect of the present disclosure.
[0007] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the present disclosure, nor is it intended to limit the scope of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, wherein like reference numerals generally represent like components throughout the exemplary embodiments of the present disclosure.
[0009] Figure 1 A schematic diagram illustrating an environment in which embodiments of the present disclosure may be implemented;
[0010] Figure 2 A flowchart illustrating a process of task management according to an embodiment of the present disclosure is shown;
[0011] Figure 3 A schematic diagram illustrating the time consumption of determining a backup task according to an embodiment of the present disclosure is illustrated;
[0012] Figure 4 A flowchart of a process of determining a first backup task group according to an embodiment of the present disclosure is illustrated;
[0013] Figure 5 A flowchart illustrating a process of determining the time consumption of a backup task according to an embodiment of the present disclosure; and
[0014] Figure 6 A schematic block diagram of an example device that may be used to implement embodiments of the present disclosure is illustrated. DETAILED DESCRIPTION
[0015] The preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the preferred embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.
[0016] As used herein, the term "including" and its variations mean open inclusion, i.e., "including but not limited to". Unless otherwise stated, the term "or" means "and / or". The term "based on" means "based at least in part on". The terms "an example embodiment" and "an embodiment" mean "at least one example embodiment". The term "another embodiment" means "at least one additional embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may also be included below.
[0017] As described above, people hope to be able to predict the time required for backup operations. Traditional solutions can predict the time required for backup operations to be performed based on historical backup operations. For example, some traditional solutions determine the predicted time required for backup operations by storing the amount and time of historical backup data, and the historical backup data records need to be traversed during the prediction process. Such solutions need to store a large amount of historical data, and as the amount of data increases, the time required for the prediction process will also increase. Considering the timeliness required for backup operations, the long time required for predicting backup operations may be unacceptable.
[0018] According to an embodiment of the present disclosure, a task management scheme is provided. In the scheme, an execution plan associated with multiple backup tasks including a target backup task is obtained, and the execution plan at least indicates the backup data volume and start time of the multiple backup tasks; based on the execution plan, a first group of backup tasks to be executed in parallel at the start time of the target backup task is determined; a predicted backup speed for executing the first group of backup tasks in parallel at the start time of the target backup task is determined; and the time required to execute the target backup task is determined based at least on the predicted backup speed and the backup data volume of the target backup task. By considering the situation of backup tasks executed in parallel at different times, the embodiment of the present disclosure can more accurately predict the time required to execute the backup task.
[0019] Figure 1 1 is a schematic diagram of an environment 100 in which embodiments of the present disclosure may be implemented. Figure 1 As shown, the environment 100 includes a computing device 120 and a backup storage device 130. The computing device 120 can receive one or more backup tasks to be executed, and write the data to the backup storage device 130 after pre-processing the data to be backed up. Specifically, the computing device 120 can, for example, divide the data to be backed up into blocks according to a predetermined size, and such a size can be configured accordingly according to the requirements of different backup systems.
[0020] Subsequently, the computing device 120 may also determine, for example, based on the hash value of the data in each data block, whether the data in the data block has been stored in the backup storage device 130. If the data in the data block has been stored in the backup storage device 130, the computing device 120 may avoid repeatedly writing the data block. Instead, the computing device 120 may write the data block and record the hash value of the data block for the next backup de-redundancy operation.
[0021] Considering that the computing device 120 may execute different numbers and types of backup tasks in parallel at different times, the backup speed at different times may also change. The computing device 120 can determine the time required to execute each backup task in the backup task based on the execution plan of the backup task 110, thereby providing support for users or developers to better plan their work.
[0022] The following will refer to Figures 2 to 5 The process of task management according to an embodiment of the present disclosure is described below. Figure 2 FIG. 2 is a flowchart of a method 200 for task management according to some embodiments of the present disclosure. The method 200 may be performed by Figure 1 For the convenience of discussion, the following will be combined with Figure 1 Method 200 is described.
[0023] In box 202, the computing device 120 obtains an execution plan associated with multiple backup tasks including a target backup task, and the execution plan at least indicates the backup data volume and start time of the multiple backup tasks. In some embodiments, the computing device 120 can receive multiple backup tasks 110 submitted by one or more users. Generally, the user will specify the start time when the backup task 110 is expected to be executed. The computing device 120 can also determine the backup data volume of the backup task 110 when receiving the backup task 110, such as 100GB. Such information can be organized as a separate file, for example, to indicate the execution plan of the backup task 110.
[0024] Figure 3 A schematic diagram 300 is shown of a process of determining the time consumption of executing a target backup task according to an embodiment of the present disclosure. Figure 3As an example, as shown in the figure, the computing device 120 may receive, for example, a first task 310, a second task 320, a third task 330, a fourth task 340, and a fifth task 350, wherein the fourth task 340 may be, for example, a target backup task whose time consumption is to be determined (i.e., the fourth task 340). The computing device 120 may determine from the execution plan that the start time of the first task 310 and the second task 320 is t0, the start time of the third task 330 and the fourth task 340 is t1, and the start time of the fifth task 350 is t5. For the convenience of description, the backup data volumes of the first task 310 to the fifth task 350 may be represented as s1, s2, s3, s4, and s5.
[0025] Continue to refer Figure 2 At block 204, the computing device 120 determines, based on the execution plan, a first set of backup tasks to be executed in parallel at the start time of the target backup task. Figure 3 For example, the starting time of the target backup task (ie, the fourth task 340) is t1, and the computing device 120 can determine the first set of backup tasks to be executed at time t1 according to the execution plan. Figure 4 To describe the specific process of block 204, Figure 4 A flowchart of a process of determining a first group of backup tasks according to an embodiment of the present disclosure is shown.
[0026] like Figure 4 As shown, in block 402, the computing device 120 may determine a previous backup task among the plurality of backup tasks whose start time is earlier than the start time of the target backup task. Figure 3 As an example, the computing device 120 may determine from a plurality of backup tasks (the first task 310 to the fifth task 350 ) that the backup tasks whose start times are earlier than t1 include the first task 310 and the second task 320 (their start times are both t0 ).
[0027] In block 404, computing device 120 may determine whether the previous backup task will be completed before the start time of the target backup task based on the start time of the previous backup task and the amount of backup data. In response to determining in block 404 that the previous backup task will not be completed before the start time of the target backup task, the method proceeds to block 406, where computing device 120 may add the previous backup task to the first group of backup tasks.
[0028] continue Figure 3For example, for the first task 310 and the second task 320 whose start time is earlier than t1. The computing device 120 can determine whether the first task 310 and the second task 320 will be completed before t1. Specifically, the computing device 120 can first determine the backup speed of executing the first task 310 and the second task 320 in parallel. In some embodiments, the computing device 120 can, for example, determine the backup speed based on historical backup situations. For example, the computing device 120 can determine the backup speed by determining the speed of the backup task that is close to the backup data volume of the first task 310 and the second task 320 from the historical backup situations. In some embodiments, the computing device 120 can also determine the backup speed of executing the first task 310 and the second task 320 in parallel based on a machine learning method.
[0029] After determining the backup speed of the first task 310 and the second task 320 being performed in parallel, the computing device 120 may determine their predicted completion time based on the backup data volume s1 of the first task 310 and the backup data volume s2 of the second task 320, and determine whether the time is later than the start time t1 of the target backup task (i.e., the fourth task 340). When it is determined that the predicted completion time is later than the start time t1, the computing device 120 may add the first task 310 and the second task 320 to the first group of backup tasks.
[0030] Additionally, the computing device 120 will also determine other backup tasks among the multiple backup tasks that are started simultaneously with the target backup task based on the execution plan. Figure 3 For example, the computing device 120 may also add the third task 330, which also starts at time t1, to the first group of backup tasks. Thus, the computing device 120 may determine that the first group of backup tasks that need to be executed in parallel at time t1 include the first task 310, the second task 320, the third task 330, and the target backup task (i.e., the fourth task 340).
[0031] Continue to refer Figure 2 In block 206, computing device 120 determines a predicted backup speed for executing the first set of backup tasks in parallel at the start time of the target backup task. In some embodiments, computing device 120 may determine the predicted backup speed based on specific information of each backup task in the first set of backup tasks.
[0032] In some embodiments, computing device 120 may first obtain a metric associated with the first group of backup tasks. In some examples, the metric may include: the number of backup tasks in the first group of backup tasks that use variable-size storage blocks, and / or the number of backup tasks in the first group of backup tasks that use fixed-size storage blocks. In data backup, one of the following two different backup modes can usually be selected: using fixed-size storage blocks or using variable-size storage blocks. Since the mechanisms of the two backup modes are different, the backup speeds of the two backup modes are also different. Therefore, the number of backup tasks in each mode will affect the backup speed.
[0033] In another example, the metric may include: the number of backup tasks with a specific backup cycle in the first group of backup tasks. Different backup cycles (e.g., backup once a month or backup once a year) will affect the proportion of data to be backed up that can pass through the de-redundancy mechanism without actually being written, and thus will also affect the final backup speed.
[0034] In another example, the metric may include: the number of concurrent threads of the first group of backup tasks. It is easy to understand that the multi-thread configuration of each backup task will also affect the final backup speed.
[0035] The computing device 120 may use one or more of the above example metrics to determine the predicted backup speed for executing the first group of backup tasks in parallel. It should be understood that any other appropriate metrics may also be used for prediction. In some embodiments, the computing device 120 may, for example, determine the functional relationship between the above metrics and the final backup speed based on historical backup situations (e.g., by function fitting), and determine the predicted backup speed based on the metrics of the first group of backup tasks.
[0036] In some embodiments, the computing device 120 may use a machine learning-based method to determine a predicted backup speed for executing the first set of backup tasks in parallel. Specifically, the computing device 120 may use a speed determination model to process metrics to determine the predicted backup speed, wherein the speed determination model is a machine learning model trained based on metrics determined from a set of reference concurrent backup tasks and corresponding actual backup speeds. Examples of machine learning models include, but are not limited to, various deep neural networks (DNNs), convolutional neural networks (CNNs), support vector machines (SVMs), decision trees, random forest models, and the like.
[0037] Specifically, the computing device 120 can, for example, obtain the above metrics of a set of backup tasks executed in parallel during the actual backup process as the input of the speed determination model, and use the actual backup speed of executing the set of concurrent tasks as the training target of the speed determination model, so that the output of the speed determination model can be close to the actual backup speed.
[0038] In some embodiments, the computing device 120 may sample the backup speeds of a group of historical concurrent backup tasks executed in parallel to obtain a group of sampled backup speeds, and determine the real backup speed based on the group of sampled backup speeds. For example, the computing device 120 may regularly sample the real backup speed with a period of 1 s, and determine the real backup speed based on the sampled group of sampled backup speeds. For example, the computing device 120 may use the mean of the group of sampled backup speeds as the real backup speed for training the speed determination model.
[0039] In some embodiments, the computing device 120 may also perform data filtering on the set of sampled backup speeds. Specifically, the computing device 120 may determine at least one sampled backup speed based on the difference between the sampled backup speeds in the set of sampled backup speeds and the sampled backup speeds at adjacent moments.
[0040] For example, the computing device 120 may calculate the difference between two adjacent sampled backup speeds in the set of sampled backup speeds. The computing device 120 may further determine the average value of the difference, and filter out sampled backup speed pairs whose difference is greater than a specific threshold (e.g., the average value of the difference), thereby determining at least one sampled backup speed from the set of sampled backup speeds. Based on this approach, some abnormal sampled speeds caused by sampling errors or other reasons may be excluded.
[0041] In some embodiments, the computing device 120 may also determine the real backup speed based on the at least one sampled backup speed. For example, the computing device 120 may calculate the mean of the at least one sampled backup speed obtained through filtering, and use the mean as the real backup speed for training the speed determination model.
[0042] Through the above training process, the speed determination model can have the ability to determine the predicted backup speed of the computing device 120 backing up the set of backup tasks in parallel from the information of the set of backup tasks executed in parallel. It should be understood that the computing device 120 can also use the speed determination model to determine the above-mentioned prediction speed of the backup task based on the metrics determined based on the first task 310 and the second task 320. Figure 3 The description determines the backup speed of executing the first task 310 and the second task 320 in parallel.
[0043] Continue to refer Figure 2 In block 208, computing device 120 determines the time required to perform the target backup task based at least on the predicted backup speed and the backup data volume of the target backup task. In some embodiments, computing device 120 may determine the time required to perform the target backup task based on the backup data volume of the target backup task and the predicted backup speed, for example.
[0044] In some embodiments, the first set of backup tasks concurrently executed by the computing device 120 before the target backup task is completed may change. For example, one of the backup tasks may have been completed or a new backup task may need to be executed. In this case, the backup speed may change. Figure 5 To describe the specific process of block 208, Figure 5 A flowchart of a process of determining a time to execute a target backup task according to an embodiment of the present disclosure is shown.
[0045] like Figure 5 As shown, at block 502, in response to at least one of the first set of backup tasks being completed or additional backup tasks being started at the intermediate time, computing device 120 may determine a second set of backup tasks to be executed in parallel at the intermediate time. Figure 3 As an example, after determining that the predicted backup speed (for the sake of convenience of description, referred to as the first predicted backup speed) of executing the first task 310, the second task 320, the third task 330 and the fourth task 340 in parallel at time t1 is p2 according to the method described above, the computing device 120 can determine the expected completion time of the first task 310 to the fourth task 340 based on the backup data volumes s1 to s4 corresponding to the first task 310 to the fourth task 340.
[0046] For example, for the first task 310 and the second task 320, the computing device 120 may determine the amount of data that has been completed previously, and calculate the remaining amount of data that needs to be backed up at time t1, and determine the remaining backup time based on the remaining amount of data and the first predicted backup speed p2. For example, the computing device 120 may determine that the second task 320 is expected to take w2 hours to complete the backup, and determine that it is the first to be completed among the first task 310 to the fourth task 340.
[0047] Based on this determination, computing device 120 may determine that the backup tasks executed in parallel at time t2 (ie, t1+w2) will change. Specifically, computing device 120 may determine that the second set of backup tasks to be executed in parallel at time t2 only includes first task 310, third task 330, and fourth task 340.
[0048] At block 504, computing device 120 may determine a second predicted backup speed at which the second set of backup tasks will be performed in parallel. In some embodiments, computing device 120 may, for example, use the method described above with reference to block 206 to determine the second predicted backup speed. Specifically, computing device 120 may determine a metric for the second set of backup tasks and process the metric using a speed determination model to determine the second predicted backup speed. Figure 3For example, the computing device 120 may determine that the second predicted backup speed of executing the first task 310, the third task 330, and the fourth task 340 in parallel is p2.
[0049] At block 506, computing device 120 may determine the time required to perform the target backup task based on the first predicted backup speed and the second predicted backup speed. In some embodiments, computing device 120 may, for example, first determine the amount of backup data that has been completed between the start time and the intermediate time, and determine the amount of remaining data that needs to be backed up from the intermediate time. Figure 3 For example, the computing device 120 may determine that from t1 to t2, the computing device 120 has completed the backup data volume w2*p2, and the remaining backup data volume of the target backup task (ie, the fourth task 340) is s4-w2*p2.
[0050] Further, the computing device 120 can determine that the time required to complete the target backup task (ie, the fourth task 340) is w2+(s4-w2*p2) / p3 according to the second predicted backup speed p2 and the remaining backup data volume s4-w2*p2.
[0051] It should be understood that the computing device 120 may iteratively perform the process of blocks 502 to 506 to more accurately determine the time required to perform the target backup task. Figure 3 For example, based on the predicted backup speed p3, the computing device 120 can determine that the first task 310 will complete the backup at time t3, that is, the computing device 120 can determine that the backup tasks that need to be performed in parallel at time t3 will only include the third task 330 and the fourth task 340. The computing device 120 can further determine that the predicted backup speed for performing the third task 330 and the fourth task 340 in parallel is p4 based on the metric determined based on the third task 330 and the fourth task 340.
[0052] like Figure 3 As shown, further, after determining that the predicted backup speed of executing the third task 330 and the fourth task 340 in parallel is p4, the computing device 120 can, for example, determine that the third task 330 will be completed at time t4. That is, the computing device 120 can determine that the backup tasks that will be required to be parallel at time t4 will only include the fourth task 340. The computing device 120 can further determine the predicted backup speed p5 of executing the fourth task 340 alone based on the metric determined from the fourth task 340.
[0053] like Figure 3As shown, further, the computing device 120 may also determine that at time t5, the fifth backup task 350 will begin to be executed. That is, the computing device 120 may determine that the backup tasks that need to be executed in parallel at time t3 will include the fourth task 340 and the fifth task 350. The computing device 120 may further determine the predicted backup speed p6 for executing the fourth task 340 and the fifth task 350 based on the metric determined from the fourth task 340.
[0054] like Figure 3 As shown, further, the computing device 120 can determine that the fourth task 340 will be completed at t6, and the backup tasks executed in parallel before this will not change. At this time, the computing device 120 can determine t6 as the time when the fourth backup task 340 is expected to be completed.
[0055] Based on the process described above, the computing device 120 can determine that the time required to execute and complete the target backup task (i.e., the fourth task 340) is: w2+w3+w4+w5+w6, wherein w2 is determined based on the remaining data amount of the second task 320 at time t1 and the predicted backup speed p2, w3 is determined based on the remaining data amount of the first task 310 at time t2 and the predicted backup speed p3, w4 is determined based on the remaining data amount of the third task 330 at time t3 and the predicted backup speed p4, w5 is determined based on the start time of the fifth task 350, and w6 is determined based on the remaining data amount of the fourth task 340 at time t5 and the predicted backup speed p6.
[0056] Based on the above scheme, the embodiments of the present disclosure can determine different backup speeds in different time periods according to the specific circumstances of the backup tasks executed in parallel in different time periods, so as to more accurately predict the time required to execute the backup tasks, thereby providing better support for user planning work.
[0057] In some embodiments, computing device 120 may also provide the determined time required to execute the target backup task in the form of text, graphics, audio, or video, so that the user can more intuitively understand the time required for the submitted backup task and thus better arrange the work to be done.
[0058] Figure 6 6 is a schematic block diagram of an example device 600 that can be used to implement an embodiment of the present disclosure. Figure 1The computing device 120 shown can be implemented by device 600. As shown, device 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to computer program instructions stored in a read-only memory (ROM) 602 or loaded from a storage unit 608 into a random access memory (RAM) 603. In RAM 603, various programs and data required for the operation of device 600 can also be stored. CPU 601, ROM 602 and RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to bus 604.
[0059] A number of components in the device 600 are connected to the I / O interface 605, including: an input unit 606, such as a keyboard, a mouse, etc.; an output unit 607, such as various types of displays, speakers, etc.; a storage unit 608, such as a disk, an optical disk, etc.; and a communication unit 609, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.
[0060] The various processes and processing described above, such as method 200, may be performed by processing unit 601. For example, in some embodiments, method 200 may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program may be loaded and / or installed on device 600 via ROM 602 and / or communication unit 609. When the computer program is loaded into RAM 603 and executed by CPU 601, one or more actions of method 200 described above may be performed.
[0061] The present disclosure may be a method, an apparatus, a system and / or a computer program product. The computer program product may include a computer-readable storage medium carrying computer-readable program instructions for executing various aspects of the present disclosure.
[0062] A computer-readable storage medium may be a tangible device that can hold and store instructions used by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples of computer-readable storage media (a non-exhaustive list) include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, such as a punch card or a raised structure in a groove on which instructions are stored, and any suitable combination of the foregoing. As used herein, a computer-readable storage medium is not to be interpreted as a transient signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse through a fiber optic cable), or an electrical signal transmitted through a wire.
[0063] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in the computer-readable storage medium in each computing / processing device.
[0064] The computer program instructions for performing the operation of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages, such as Smalltalk, C++, etc., and conventional procedural programming languages, such as "C" language or similar programming languages. Computer-readable program instructions may be executed completely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer, partially on a remote computer, or completely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., using an Internet service provider to connect via the Internet). In some embodiments, an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may be customized by utilizing the state information of the computer-readable program instructions, and the electronic circuit may execute the computer-readable program instructions, thereby realizing various aspects of the present disclosure.
[0065] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.
[0066] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0067] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operating steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0068] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of the module, program segment or instruction includes one or more executable instructions for realizing the specified logical function. In some alternative implementations, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or action, or can be implemented with a combination of special hardware and computer instructions.
[0069] The embodiments of the present disclosure have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.
Claims
1. A task management method, include: Sample the backup speed of a set of historical concurrent backup tasks executed in parallel to obtain the actual backup speed; Acquire an execution plan associated with a plurality of backup tasks including a target backup task having backup data, the execution plan at least indicating start times of the plurality of backup tasks and a backup data volume of the target backup task submitted by a user; Based on the execution plan, determining a first group of backup tasks to be executed in parallel at the start time of the target backup task; Obtaining a metric of the first group of backup tasks, the metric comprising the number of backup tasks in the first group of backup tasks that use fixed-size storage blocks and the number of backup tasks in the first group of backup tasks that use variable-size storage blocks; Determine, based on the metric and the actual backup speed, a predicted backup speed for executing the first group of backup tasks in parallel at the start time of the target backup task; as well as The time required to execute the target backup task is determined based at least on the predicted backup speed and the backup data volume of the target backup task.
2. The task management method according to claim 1, wherein determining the first group of backup tasks include: Determine a previous backup task among the multiple backup tasks whose start time is earlier than the start time of the target backup task; Based on the start time of the previous backup task and the amount of backup data, determining whether the previous backup task will be completed before the start time of the target backup task; as well as In response to determining that the preceding backup task will not be completed before the start time of the target backup task, the preceding backup task is added to the first set of backup tasks.
3. The task management method according to claim 1, wherein determining the predicted backup speed include: Obtaining a metric associated with the first group of backup tasks, the metric further comprising at least one of the following: the number of backup tasks with a specific backup period in the first group of backup tasks and the number of concurrent threads of the first group of backup tasks; as well as The predicted backup speed is determined based on the metric.
4. The task management method according to claim 3, wherein the predicted backup speed is determined based on the metric include: The metrics are processed using a speed determination model to determine the predicted backup speed, wherein the speed determination model is a machine learning model trained based on the metrics determined from a set of reference concurrent backup tasks and corresponding true backup speeds.
5. The task management method according to claim 4, further comprising determining the actual backup speed by the following steps: Sampling the backup speeds of the set of historical concurrent backup tasks executed in parallel to obtain a set of sampled backup speeds; Determine at least one sampling backup speed based on a difference between a sampling backup speed in the set of sampling backup speeds and a sampling backup speed at an adjacent time; as well as The actual backup speed is determined based on the at least one sampled backup speed.
6. The task management method according to claim 1, wherein the predicted backup speed is a first predicted backup speed, wherein the time required to execute the target backup task is determined: In response to at least one of the first set of backup tasks being completed or an additional backup task being started at the intermediate time, determining a second set of backup tasks to be executed in parallel at the intermediate time; determining a second predicted backup speed at which the second set of backup tasks will be executed in parallel; as well as The time required to execute the target backup task is determined based on the first predicted backup speed and the second predicted backup speed.
7. The task management method according to claim 1, further comprising: include: The time required to perform the target backup task is provided by using at least one of the following: text, graphics, audio, or video.
8. An electronic device, include: at least one processing unit; at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions, when executed by the at least one processing unit, causing the apparatus to perform actions comprising: Sample the backup speed of a set of historical concurrent backup tasks executed in parallel to obtain the actual backup speed; Acquire an execution plan associated with a plurality of backup tasks including a target backup task having backup data, the execution plan at least indicating start times of the plurality of backup tasks and a backup data volume of the target backup task submitted by a user; Based on the execution plan, determining a first group of backup tasks to be executed in parallel at the start time of the target backup task; Obtaining a metric of the first group of backup tasks, the metric comprising the number of backup tasks in the first group of backup tasks that use fixed-size storage blocks and the number of backup tasks in the first group of backup tasks that use variable-size storage blocks; Determining a predicted backup speed for executing the first group of backup tasks in parallel at a start time of the target backup task based on the metric and the actual backup speed; and The time required to execute the target backup task is determined based at least on the predicted backup speed and the backup data volume of the target backup task.
9. The electronic device according to claim 8, wherein determining the first set of backup tasks include: Determine a previous backup task among the multiple backup tasks whose start time is earlier than the start time of the target backup task; Based on the start time of the previous backup task and the amount of backup data, determining whether the previous backup task will be completed before the start time of the target backup task; as well as In response to determining that the preceding backup task will not be completed before the start time of the target backup task, the preceding backup task is added to the first set of backup tasks.
10. The electronic device of claim 8, wherein determining the predicted backup speed include: Obtaining a metric associated with the first group of backup tasks, the metric further comprising at least one of the following: the number of backup tasks with a specific backup period in the first group of backup tasks and the number of concurrent threads of the first group of backup tasks; as well as The predicted backup speed is determined based on the metric.
11. The electronic device of claim 10, wherein the predicted backup speed is determined based on the metric include: The metrics are processed using a speed determination model to determine the predicted backup speed, wherein the speed determination model is a machine learning model trained based on the metrics determined from a set of reference concurrent backup tasks and corresponding true backup speeds.
12. The electronic device according to claim 11, further comprising determining the actual backup speed by the following steps: Sampling the backup speeds of the set of historical concurrent backup tasks executed in parallel to obtain a set of sampled backup speeds; Determine at least one sampling backup speed based on a difference between a sampling backup speed in the set of sampling backup speeds and a sampling backup speed at an adjacent time; as well as The actual backup speed is determined based on the at least one sampled backup speed.
13. The electronic device according to claim 8, wherein the predicted backup speed is a first predicted backup speed, wherein determining the time required to perform the target backup task: In response to at least one of the first set of backup tasks being completed or an additional backup task being started at the intermediate time, determining a second set of backup tasks to be executed in parallel at the intermediate time; determining a second predicted backup speed at which the second set of backup tasks will be executed in parallel; as well as The time required to execute the target backup task is determined based on the first predicted backup speed and the second predicted backup speed.
14. The electronic device according to claim 8, further comprising: include: The time required to perform the target backup task is provided by using at least one of the following: text, graphics, audio, or video.
15. A computer program product stored in a non-transitory computer storage medium and comprising machine executable instructions which, when executed in a device, cause the device to perform operations, the operations include: Sample the backup speed of a set of historical concurrent backup tasks executed in parallel to obtain the actual backup speed; Acquire an execution plan associated with a plurality of backup tasks including a target backup task having backup data, the execution plan at least indicating start times of the plurality of backup tasks and a backup data volume of the target backup task submitted by a user; Based on the execution plan, determining a first group of backup tasks to be executed in parallel at the start time of the target backup task; Obtaining a metric of the first group of backup tasks, the metric comprising the number of backup tasks in the first group of backup tasks that use fixed-size storage blocks and the number of backup tasks in the first group of backup tasks that use variable-size storage blocks; Determine, based on the metric and the actual backup speed, a predicted backup speed for executing the first group of backup tasks in parallel at the start time of the target backup task; as well as The time required to execute the target backup task is determined based at least on the predicted backup speed and the backup data volume of the target backup task.
16. The computer program product of claim 15, wherein determining the first set of backup tasks include: Determine a previous backup task among the multiple backup tasks whose start time is earlier than the start time of the target backup task; Based on the start time of the previous backup task and the amount of backup data, determining whether the previous backup task will be completed before the start time of the target backup task; as well as In response to determining that the preceding backup task will not be completed before the start time of the target backup task, the preceding backup task is added to the first set of backup tasks.
17. The computer program product of claim 15, wherein determining the predicted backup speed include: Obtaining a metric associated with the first group of backup tasks, the metric further comprising at least one of the following: the number of backup tasks with a specific backup period in the first group of backup tasks and the number of concurrent threads of the first group of backup tasks; as well as The predicted backup speed is determined based on the metric.
18. The computer program product of claim 17, wherein the predicted backup speed is determined based on the metric include: The metrics are processed using a speed determination model to determine the predicted backup speed, wherein the speed determination model is a machine learning model trained based on the metrics determined from a set of reference concurrent backup tasks and corresponding true backup speeds.
19. The computer program product of claim 18, the operations further comprising determining the actual backup speed by: Sampling the backup speeds of the set of historical concurrent backup tasks executed in parallel to obtain a set of sampled backup speeds; Determine at least one sampling backup speed based on a difference between a sampling backup speed in the set of sampling backup speeds and a sampling backup speed at an adjacent time; as well as The actual backup speed is determined based on the at least one sampled backup speed.
20. The computer program product of claim 15, wherein the predicted backup speed is a first predicted backup speed, wherein determining the time required to perform the target backup task: In response to at least one of the first set of backup tasks being completed or an additional backup task being started at the intermediate time, determining a second set of backup tasks to be executed in parallel at the intermediate time; determining a second predicted backup speed at which the second set of backup tasks will be executed in parallel; as well as The time required to execute the target backup task is determined based on the first predicted backup speed and the second predicted backup speed.
