Task scheduling method and platform based on Windows system resources, storage medium and equipment
By identifying task types and resource requirements and scheduling tasks to appropriate Windows instances for execution, the problems of low resource utilization and relying on manual management in the prior art are solved, and more efficient resource utilization and task processing efficiency are achieved.
Patent Information
- Application Number
- CN202411362739.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-27
- Publication Date
- 2025-02-14
AI Technical Summary
The existing Windows task scheduling system cannot fully utilize the resources of multiple Windows instances, and task scheduling and resource scheduling rely on manual management, making it difficult to automate and dynamically adjust, resulting in low resource utilization and low efficiency.
Provide a task scheduling method based on Windows system resources, identify task types and resource requirements by receiving multiple tasks submitted by users, and schedule tasks to be executed on an appropriate Windows instance based on this information. This method includes comparing the resource requirements of the task with the remaining resources of the Windows instance, automatically scheduling the task, and rescheduling the task when there is an exception in the Windows instance pool.
By making full use of the computing resources of multiple Windows instances, we can improve resource utilization efficiency, reduce costs, and automatically allocate appropriate resources according to different task types to improve task processing efficiency.
Smart Images
Figure CN119440751A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer application technology, and in particular to a task scheduling method, platform, storage medium and device based on Windows system resources. Background Art
[0002] Nowadays, resource reuse technology applied to the cloud has been widely used in software development, testing or data analysis. Resource reuse can refer to the efficient sharing and reuse of Windows operating system resources, such as computing power or network resources, in a cloud computing environment, so as to provide services to multiple users while optimizing resource utilization and reducing costs. These resource scheduling is often achieved through the Windows task scheduling system.
[0003] However, most existing Windows task scheduling systems are based on a single Windows instance and cannot fully utilize the resources of multiple Windows instances. At the same time, task scheduling and resource scheduling usually rely on manual management, which is difficult to automate and dynamically adjust. Summary of the invention
[0004] The purpose of this application is to provide a task scheduling method, platform, storage medium and device based on Windows system resources to solve the technical problem of low resource utilization of existing task scheduling systems in the prior art, thereby affecting efficiency. The preferred technical solutions among the many technical solutions provided in this application can produce many technical effects as described below.
[0005] To achieve the above objectives, this application provides the following technical solutions:
[0006] The first aspect of the present application provides a task scheduling method based on Windows system resources, including: receiving multiple tasks submitted by a user and identifying each task; scheduling each task to be executed on a Windows instance according to the task type and resource requirements corresponding to each task; obtaining the execution status and execution results of each task on the Windows instance, and locking the resources occupied by each task.
[0007] In some embodiments, the task type includes at least one of a desktop task, a stand-alone background task, and a composite background task.
[0008] In some embodiments, each task is scheduled to be executed on a Windows instance according to the task type and resource requirements corresponding to each task, including: if the task type corresponding to the task is the desktop type task, the task is scheduled to be executed on a Windows instance where the desktop type task does not exist in the current task queue; if the task type corresponding to the task is the stand-alone background type task, the task is scheduled to be executed on the Windows instance with the most remaining resources; if the task type corresponding to the task is the composite background type task, the task is scheduled to be executed on multiple Windows instances in parallel.
[0009] In some embodiments, the method further includes: comparing the resource requirements of the task with the remaining resources of the Windows instance, and scheduling the task to be executed on the Windows instance according to the comparison result.
[0010] In some embodiments, the method also includes: if there is an abnormality in the Windows instance pool where the Windows instance is located, stopping scheduling tasks to all Windows instances in the Windows instance pool; if there is an abnormality in one or more of the Windows instances in the Windows instance pool, rescheduling all tasks in the task queues of one or more of the Windows instances.
[0011] In some embodiments, the method further includes: isolating resources used by each task in the task queue of the Windows instance.
[0012] In some embodiments, the Windows instance includes a computer, a server, and an operating environment isolated on the computer or the server using container or virtual machine technology.
[0013] The second aspect of the present application provides a Windows system resource scheduling platform, which is used to execute the task scheduling method based on Windows system resources as described above, and the Windows system resource scheduling platform includes: a scheduling center and a Windows instance pool; wherein the Windows instance pool has multiple Windows instances for providing computing resources, and the Windows instance includes a task manager; the scheduling center is configured to receive multiple tasks submitted by a user, identify each task, and schedule each task to be executed on the Windows instance according to the task type and resource requirements corresponding to each task; the task manager is configured to monitor the execution status of each task on the Windows instance, and feed back the execution result of each task to the scheduling center; the task manager is used to execute tasks in the task queue of the Windows instance.
[0014] A third aspect of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed, the task scheduling method based on Windows system resources as described above is implemented.
[0015] The fourth aspect of the present application provides a processing device, comprising: one or more processors; a memory for storing one or more computer programs, and one or more of the processors are used to execute the one or more computer programs stored in the memory, so that one or more of the processors execute the task scheduling method based on Windows system resources as described above.
[0016] Implementing one of the above technical solutions of the present application has the following advantages or beneficial effects: the present application identifies multiple tasks submitted by the user, obtains the task type, and schedules each task to be executed on a different Windows instance according to the task type and resource requirements. In this case, the computing resources of multiple Windows instances can be fully utilized, resource utilization efficiency can be improved, and costs can be reduced; at the same time, appropriate resources are automatically allocated according to different task types, which can improve task processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. It is obvious that the drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:
[0018] Figure 1It is a flowchart of a task scheduling method based on Windows system resources according to an embodiment of the present application;
[0019] Figure 2 is a schematic diagram of the task types of an embodiment of the present application;
[0020] Figure 3 is a schematic diagram of scheduling desktop tasks in an embodiment of the present application;
[0021] Figure 4 It is a schematic diagram of scheduling a single-machine background task in an embodiment of the present application;
[0022] Figure 5 is a schematic diagram of scheduling a composite background task in an embodiment of the present application;
[0023] Figure 6 It is a structural block diagram of the processing device of an embodiment of the present application.
[0024] In the figure: 1. processing device; 10. memory; 11. processor. DETAILED DESCRIPTION
[0025] In order to make the purpose, technical solutions and advantages of the present application clearer, the various exemplary embodiments to be described below will refer to the corresponding drawings, which constitute a part of the exemplary embodiments, wherein various exemplary embodiments that may be used to implement the present application are described. Unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation methods described in the following exemplary embodiments do not represent all implementation methods consistent with the present disclosure. It should be understood that they are only examples of processes, methods, and devices that are consistent with some aspects disclosed in the present application as detailed in the attached claims, and other embodiments may also be used, or the embodiments listed herein may be modified in structure and function without departing from the scope and essence of the present application.
[0026] In the description of the present application, it should be understood that the terms "center", "longitudinal", "lateral", etc. indicate the orientation or positional relationship based on the drawings, which is only for the convenience of describing the present application and simplifying the description, rather than indicating or implying that the elements referred to must have a specific orientation, be constructed and operated in a specific orientation. The terms "first", "second", etc. are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. The term "multiple" means two or more. The terms "connected" and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, an integral connection, a mechanical connection, an electrical connection, a communication connection, a direct connection, an indirect connection through an intermediate medium, and can be the internal connection of two elements or the interaction relationship between two elements. The term "and / or" includes any and all combinations of one or more related listed items. For those of ordinary skill in the art, the specific meanings of the above terms in the present application can be understood according to the specific circumstances.
[0027] In order to illustrate the technical solution described in the present application, a specific embodiment is provided below, and only the parts related to the embodiment of the present application are shown.
[0028] like Figure 1 As shown, the present application provides a task scheduling method based on Windows system resources, which may include the following steps (step S1 to step S3):
[0029] S1. Receive multiple tasks submitted by users and identify each task.
[0030] In some embodiments, users can submit tasks to the cloud through a web service interface, a mobile application API, or a mobile client. The cloud can simultaneously receive multiple tasks from different users and identify the multiple tasks sequentially or in parallel. In some embodiments, the multiple tasks may refer to tasks transmitted from a local computer to the cloud, or from the cloud to a local computer.
[0031] In some embodiments, the task type may include at least one of a desktop task, a stand-alone background task, and a composite background task.
[0032] In some embodiments, a desktop task may refer to a task that directly interacts with the user and is performed in the user's desktop environment. For example, a desktop task may be playing a video in full screen or running a game, image editing, word processing, or instant messaging, etc. A stand-alone background task may refer to a task that is performed on a single computer. A stand-alone background task may not require direct user interaction and may run in the background. For example, a stand-alone background task may be playing music, downloading files, video transcoding, or disk cleaning, etc. A composite background task may refer to a task that needs to be performed across multiple computers or network resources, such as distributed computing, big data analysis, or batch downloading of subtasks, etc.
[0033] In some embodiments, Figure 2 As shown, an identifier and a number may be added to the task type. Specifically, the identifier of a desktop task may be A, the identifier of a stand-alone background task may be B, and the identifier of a composite background task may be C. For example, a desktop task may be represented as A5.
[0034] S2. Schedule each task to be executed on the Windows instance according to the task type and resource requirements corresponding to each task.
[0035] In some embodiments, resource requirements may include CPU, GPU, memory, network, and storage usage. For example, task A1 submitted by a user, i.e., a desktop task, may have resource requirements of 1G memory, 100M network, 50MB hard disk, 200M video memory, and 20% CPU. Task B1 submitted by a user, i.e., a stand-alone background task, may have resource requirements of 2G memory, 10G hard disk, 2G video memory, 200% CPU, and 0M network.
[0036] In some embodiments, a Windows instance may include a computer, a server, and an operating environment isolated on a computer or server using container or virtual machine technology. A Windows instance may be used to execute tasks. Tasks may be scheduled to be executed on different Windows instances. A Windows instance may have a task queue, and a Windows instance may process tasks in the task queue sequentially or in parallel. A Windows instance may be used to provide schedulable Windows computing resources.
[0037] In some embodiments, a container may refer to running multiple isolated application instances within the same operating system. A virtual machine is a technology used to virtualize a computing environment and can be used to simulate hardware devices such as a CPU or a network device to virtualize a computer.
[0038] In some embodiments, a task scheduling method based on Windows system resources may include: comparing the resource requirements of the task with the remaining resources of the Windows instance, and scheduling the task to be executed on the Windows instance according to the comparison result. Specifically, if the resource requirements of the task are less than the remaining resources of the Windows instance, the task can be scheduled to be executed on the Windows instance. If the task is a composite background task, the resource requirements of the subtasks split from the composite background task can be compared with the remaining resources of multiple different Windows instances, and then each subtask can be scheduled to be executed on a different Windows instance.
[0039] In some embodiments, each task is scheduled to be executed on a Windows instance according to the task type and resource requirements corresponding to each task, which may include: if the task type corresponding to the task is a desktop task, the task is scheduled to be executed on a Windows instance where no desktop task exists in the current task queue.
[0040] In some embodiments, the task queue of each Windows instance can be obtained, one or more Windows instances without desktop tasks in the current task queue can be filtered out, and then the task can be scheduled to be executed on one of the Windows instances. Figure 3 As shown, if there is no desktop task in Windows instance 2, desktop task A5 can be scheduled to Windows instance 2. In some embodiments, the task can be scheduled to be executed on a Windows instance with the most remaining resources among multiple Windows instances without desktop tasks.
[0041] If the task type corresponding to the task is a stand-alone background task, the task can be scheduled to be executed on the Windows instance with the most remaining resources.
[0042] In some embodiments, the resource status and remaining resource status of each Windows instance can be recorded in real time. For example, Windows instance 2 can have 16G memory, 8-core CPU, 12G video memory, 2T hard disk and 1G network. The remaining resource status can be obtained by subtracting the resource requirements of the tasks in the task queue from the resource status of the Windows instance. Figure 4 As shown, if Windows instance 2 is the idlest Windows instance, that is, the Windows instance with the most remaining resources, the stand-alone background task can be scheduled to be executed on Windows instance 2. In some embodiments, the remaining resource situation of the Windows instance can also refer to the current resource situation of the Windows instance.
[0043] If the task type corresponding to the task is a composite background task, the task is scheduled to be executed in parallel on multiple Windows instances.
[0044] In some embodiments, the composite background task can be split into multiple subtasks, and the multiple subtasks can be scheduled to different Windows instances for parallel execution. Figure 5 As shown, the composite background task C9 can be scheduled to be executed in parallel on Windows instance 1 and Windows instance 2.
[0045] In some embodiments, desktop tasks can be run exclusively on a single Windows instance. Standalone background tasks can be run concurrently on a single Windows instance. Composite background tasks can be run in parallel across multiple Windows instances.
[0046] In some embodiments, the task scheduling method based on Windows system resources may include: if there is an abnormality in the Windows instance pool where the Windows instance is located, then stop scheduling tasks to all Windows instances in the Windows instance pool; if there is an abnormality in one or more Windows instances in the Windows instance pool, then reschedule all tasks in the task queues of one or more Windows instances. In some embodiments, the abnormality in the Windows instance pool may refer to a failure to create a Windows instance, a failure to start a Windows instance, a resource allocation error, or improper network policy configuration. The abnormality in the Windows instance may refer to performance degradation, inability to access network resources, exhaustion of disk space, or update failure.
[0047] In some embodiments, when one or more Windows instances in a Windows instance pool are abnormal, tasks in the task queue of the abnormal Windows instance can be dispatched to other Windows instances in the same Windows instance pool for execution. Tasks in the task queue of the abnormal Windows instance can also be dispatched to another or multiple Windows instance pools.
[0048] In some embodiments, multiple tasks may be scheduled to multiple different Windows instance pools, each of which may include at least one Windows instance.
[0049] In some embodiments, the task scheduling method based on Windows system resources may include: isolating the resources used by each task in the task queue of the Windows instance. That is, the tasks in the task queue of each Windows instance are independent when using the computing resources of the Windows instance. Thus, the mutual influence between tasks can be reduced.
[0050] As described above, allocating tasks to different Windows instances for execution according to task types and resource requirements can make task scheduling more flexible and resource allocation more reasonable and efficient.
[0051] S3. Obtain the execution status and results of each task on the Windows instance, and lock the resources occupied by each task.
[0052] In some embodiments, when a Windows instance receives a task, the resources occupied by the task executed on the Windows instance can be locked. The current resource status of the Windows instance can be dynamically updated and obtained based on the execution status or execution result of each task in the Windows instance to facilitate subsequent task scheduling. For example, when the task is completed, the current resource status of the Windows instance can be updated in a timely manner to obtain the remaining resource status of the Windows instance.
[0053] The present application also provides a Windows system resource scheduling platform, which can be used to execute the task scheduling method based on Windows system resources as described above. The Windows system resource scheduling platform may include: a scheduling center and a Windows instance pool; wherein the Windows instance pool may include multiple Windows instances for providing computing resources, and the Windows instance may include a task manager.
[0054] In some embodiments, the scheduling center can be configured to receive multiple tasks submitted by users, identify each task, and schedule each task to be executed on a Windows instance according to the task type and resource requirements corresponding to each task. The scheduling center can be set in the cloud or a local server. In some embodiments, the local server can send tasks to the scheduling center in the cloud. The scheduling center can be connected to multiple Windows instance pools to schedule tasks to be executed on Windows instances in the Windows instance pool.
[0055] In some embodiments, the task manager can be configured to monitor the execution of each task on the Windows instance, and feed back the execution status and execution results of each task to the scheduling center. The task manager can be used to execute tasks in the task queue of the Windows instance.
[0056] In some embodiments, the scheduling center, Windows instance pool, and task manager can be deployed using a distributed architecture, thereby improving the scalability and fault tolerance of the scheduling center, Windows instance pool, and task manager.
[0057] Those skilled in the art can understand that all or part of the features / steps of the above-mentioned method embodiments can be implemented by methods, data processing systems or computer programs, and these features can be implemented without hardware, entirely by software, or by a combination of hardware and software. The aforementioned computer program can be stored in one or more computer-readable storage media, and the storage medium stores the computer program. When the computer program is executed (such as by a processor), the steps of the above-mentioned task scheduling method embodiment based on Windows system resources are executed.
[0058] The aforementioned storage media that can store program codes include: static hard disks, solid-state hard disks, random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), optical storage devices, magnetic storage devices, flash memory, magnetic disks or optical disks and / or combinations of the above devices, that is, it can be implemented by any type of volatile or non-volatile storage device or a combination thereof.
[0059] The present application also provides an embodiment of a processing device 1, comprising one or more processors 11 and a memory 10; wherein the memory 10 is used to store one or more computer programs, and the one or more processors 11 are used to execute one or more computer programs stored in the memory 10, so that the processor 11 executes the features / steps of the above-mentioned task scheduling method embodiment based on Windows system resources.
[0060] This application identifies multiple tasks submitted by users, obtains the task type, and schedules each task to execute on different Windows instances according to the task type and resource requirements. In this case, the computing resources of multiple Windows instances can be fully utilized, resource utilization efficiency can be improved, and costs can be reduced; at the same time, appropriate resources are automatically allocated according to different task types, which can improve task processing efficiency.
[0061] The above is only the preferred embodiment of the present application. Those skilled in the art will appreciate that various changes or equivalent substitutions may be made to these features and embodiments without departing from the spirit and scope of the present application. In addition, under the guidance of the present application, these features and embodiments may be modified to adapt to specific circumstances and materials without departing from the spirit and scope of the present application. Therefore, the present application is not limited to the specific embodiments disclosed herein, and all embodiments falling within the scope of the claims of the present application belong to the protection scope of the present application.
Claims
1. A task scheduling method based on Windows system resources, characterized in that: include: Receive multiple tasks submitted by users and identify each task; Schedule each task to execute on the Windows instance according to the task type and resource requirements corresponding to each task; Obtain the execution status and results of each task on the Windows instance, and lock the resources occupied by each task.
2. The task scheduling method based on Windows system resources according to claim 1, characterized in that: The task type includes at least one of a desktop task, a stand-alone background task, and a composite background task.
3. The task scheduling method based on Windows system resources according to claim 2, characterized in that: The method schedules each task to be executed on a Windows instance according to the task type and resource requirements corresponding to each task, including: if the task type corresponding to the task is the desktop task, scheduling the task to be executed on a Windows instance where the desktop task does not exist in the current task queue; if the task type corresponding to the task is the stand-alone background task, scheduling the task to be executed on a Windows instance with the most remaining resources; if the task type corresponding to the task is the composite background task, scheduling the task to be executed on multiple Windows instances in parallel.
4. The task scheduling method based on Windows system resources according to claim 1, characterized in that: The method further includes: comparing the resource requirement of the task with the remaining resources of the Windows instance, and scheduling the task to be executed on the Windows instance according to the comparison result.
5. The task scheduling method based on Windows system resources according to claim 1, characterized in that: The method also includes: if an abnormality exists in the Windows instance pool where the Windows instance is located, stopping scheduling tasks to all Windows instances in the Windows instance pool; if an abnormality exists in one or more of the Windows instances in the Windows instance pool, rescheduling all tasks in the task queues of one or more of the Windows instances.
6. The task scheduling method based on Windows system resources according to claim 1, characterized in that: The method further includes isolating resources used by each task in the task queue of the Windows instance.
7. The task scheduling method based on Windows system resources according to claim 1, characterized in that: The Windows instance includes a computer, a server, and an operating environment isolated on the computer or the server using container or virtual machine technology.
8. A Windows system resource scheduling platform, characterized in that: The Windows system resource scheduling platform is used to execute the task scheduling method based on Windows system resources according to any one of claims 1 to 7, and the Windows system resource scheduling platform includes: a scheduling center and a Windows instance pool; wherein the Windows instance pool has multiple Windows instances for providing computing resources, and the Windows instance includes a task manager; The scheduling center is configured to receive multiple tasks submitted by users, identify each task, and schedule each task to be executed on the Windows instance according to the task type and resource requirements corresponding to each task; The task manager is configured to monitor the execution status of each task on the Windows instance, and to feed back the execution status and execution results of each task to the scheduling center; the task manager is used to execute the tasks in the task queue of the Windows instance.
9. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, which, when executed, implements the task scheduling method based on Windows system resources as described in any one of claims 1 to 7.
10. A processing device, characterized in that: include: one or more processors; A memory for storing one or more computer programs, and one or more of the processors for executing the one or more computer programs stored in the memory, so that the one or more processors execute the task scheduling method based on Windows system resources as described in any one of claims 1-7.