CN115586957A - Task scheduling system, method and device and electronic equipment - Google Patents

Task scheduling system, method and device and electronic equipment Download PDF

Info

Publication number
CN115586957A
CN115586957A CN202211490481.XA CN202211490481A CN115586957A CN 115586957 A CN115586957 A CN 115586957A CN 202211490481 A CN202211490481 A CN 202211490481A CN 115586957 A CN115586957 A CN 115586957A
Authority
CN
China
Prior art keywords
task
processed
service
service user
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202211490481.XA
Other languages
Chinese (zh)
Other versions
CN115586957B (en
Inventor
张哲�
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba China Co Ltd
Original Assignee
Alibaba China Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba China Co Ltd filed Critical Alibaba China Co Ltd
Priority to CN202211490481.XA priority Critical patent/CN115586957B/en
Publication of CN115586957A publication Critical patent/CN115586957A/en
Application granted granted Critical
Publication of CN115586957B publication Critical patent/CN115586957B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The embodiment of the application provides a task scheduling system, a method, a device and an electronic device, wherein the system comprises: the service end is applied to the task scheduling service platform, and the task processing end is used for processing tasks; the task processing end sends a first request message for requesting to distribute the task to be processed to the server end; the server side determines a target service user for acquiring the task to be processed according to the first request message and a calculation resource allocation strategy aiming at the service user; sending a second request message for requesting to acquire the task to be processed to a user side corresponding to the target service user; the method comprises the steps of obtaining a task to be processed sent by a user side, and returning a first notification message for processing the task to be processed to a task processing side. The system matches the request message sent by the task processing end with the corresponding to-be-processed task, avoids the excessive to-be-processed tasks from being accumulated on the task scheduling service platform to wait for the task processing end to execute, and improves the processing efficiency of the task processing end for processing the to-be-processed tasks.

Description

Task scheduling system, method and device and electronic equipment
Technical Field
The application relates to the technical field of task scheduling, in particular to a task scheduling system, and also relates to a task scheduling method, a task scheduling device, electronic equipment and a computer storage medium.
Background
At present, the task scheduling service platform schedules tasks according to the following procedures: and the user side sends a large number of tasks to be processed to the task scheduling service platform to request for processing the tasks to be processed. And the task scheduling service platform distributes corresponding loads to the tasks to be processed for processing in a balanced processing mode aiming at the tasks to be processed of a large number of users.
However, in the above method, the task scheduling service platform is a method for processing tasks by allocating loads to a large number of tasks to be processed, which is likely to cause a problem that the tasks to be processed are not processed in time, so that the processing efficiency of the tasks to be processed is low.
For example, in an actual application scenario of view rendering in the home decoration industry, if a task scheduling service platform receives rendering service requests of a large number of users and schedules corresponding loads for tasks to be rendered, one load is easy to be responsible for multiple tasks to be rendered, and therefore the tasks to be rendered are queued, and rendering processing efficiency is low.
Therefore, how to improve the processing efficiency of the task to be processed is a problem to be solved.
Disclosure of Invention
The embodiment of the application provides a task scheduling system to improve the processing efficiency of a task to be processed. The embodiment of the application also provides a task scheduling method and device, electronic equipment and a computer storage medium.
An embodiment of the present application provides a task scheduling system, including: the service end is applied to the task scheduling service platform, and the task processing end is used for processing tasks; the task processing end is used for sending a first request message for requesting to distribute the tasks to be processed to the server end; obtaining a first notification message which is returned by the server and used for processing the task to be processed; the server is used for determining a target service user for acquiring the task to be processed according to the first request message and a calculation power resource allocation strategy aiming at the service user; sending a second request message for requesting to acquire the task to be processed to a user side corresponding to the target service user; and obtaining the to-be-processed task sent by the user side, and returning a first notification message for processing the to-be-processed task to the task processing side.
Optionally, the server includes: a task processing type determining unit, configured to determine, according to the first request message and according to a calculation resource allocation policy for a service user, a task processing type to which a task to be processed of the service user belongs; and the target service user determining unit is used for determining the target service user for acquiring the task to be processed according to the task processing type to which the task to be processed of the service user belongs.
Optionally, the task processing type determining unit includes: the first acquisition unit is used for acquiring computing resource data set by a service user who resides in the task scheduling service platform according to the first request message; and the first determining unit is used for determining the task processing type of the task to be processed of the service user according to the computing resource data set by the service user who resides in the task scheduling service platform.
Optionally, the first determining unit includes: the second acquisition unit is used for acquiring the occupation ratio of the computational power resource data set by the service users in the task scheduling service platform according to the computational power resource data set by the service users who reside in the task scheduling service platform; and the first determining subunit is used for determining the task processing type to which the task to be rendered of the service user belongs according to the occupation ratio corresponding to the computing resource data set by the service user.
Optionally, the second obtaining unit is specifically configured to obtain computational resource data corresponding to each service user residing in the task scheduling service platform; adding and processing the computing resource data corresponding to each service user to obtain total computing resource data set by all service users who reside in the task scheduling service platform; and acquiring the ratio of the computing power resource data set by the service user in the task scheduling service platform to the computing power resource data set by all service users in the task scheduling service platform according to the ratio of the computing power resource data set by the service user who resides in the task scheduling service platform to the total computing power resource data.
Optionally, the first determining subunit is specifically configured to sort according to a proportion corresponding to the computing power resource data set by the service user; determining a service level corresponding to the service user according to the sorting order corresponding to the proportion; and determining the task processing type of the task to be processed of the service user according to the service level corresponding to the service user.
Optionally, the target service user determining unit includes: the execution priority determining unit is used for determining the execution priority of the to-be-processed tasks of the service users in the to-be-processed tasks of all the service users in the task scheduling service platform according to the task processing type to which the to-be-processed tasks of the service users belong; and the target service user determining subunit is used for determining the target service user for acquiring the task to be processed according to the execution priority of the task to be processed of the service user in the task scheduling service platform in the tasks to be processed of all the service users, wherein the execution priority corresponding to the task to be processed of the target service user is greater than the execution priority corresponding to the task to be processed of other service users.
Optionally, the target service user determination subunit is specifically configured to determine, according to a task processing type to which a task to be processed of the service user belongs, an execution sequence corresponding to the task to be processed of the service user; and determining the execution priority of the tasks to be processed of the service users in the tasks to be processed of all the service users in the task scheduling service platform according to the execution sequence corresponding to the tasks to be processed of the service users.
Optionally, the server includes: a task processing type obtaining unit, configured to obtain a to-be-processed task sent by the user side, and obtain a task processing type to which the to-be-processed task belongs; and the first notification message returning unit is used for returning a first notification message for processing the task to be processed according to the task processing type to the task processing end according to the task processing type to which the task to be processed belongs.
Optionally, the method further includes: the charging processing unit is used for determining a charging mode corresponding to the task processing type according to the task processing type to which the task to be processed belongs; and carrying out charging processing on the task to be processed according to the charging mode corresponding to the task processing type.
Optionally, the task processing end includes a plurality of loaders for executing processing services by users; and the task processing end is further configured to, after obtaining the first notification message, allocate a loader corresponding to the to-be-processed task according to the task processing type to which the to-be-processed task belongs, which is included in the first notification message.
The embodiment of the application also provides a task scheduling method, which is applied to a server of a task scheduling service platform, and the method comprises the following steps: acquiring a first request message which is sent by a task processing end for processing a task and used for requesting to distribute a task to be processed; determining a target service user for acquiring the task to be processed according to the first request message and a calculation resource allocation strategy aiming at the service user; sending a second request message for requesting to acquire the task to be processed to a user side corresponding to the target service user; and a to-be-processed task sent by the user side is obtained, and a first notification message for processing the to-be-processed task is returned to the task processing side.
Optionally, the determining, according to the first request message and according to the calculation resource allocation policy for the service user, a target service user for acquiring the task to be processed includes: according to the first request message and a calculation resource allocation strategy aiming at a service user, determining a task processing type to which a task to be processed of the service user belongs; and determining a target service user for acquiring the task to be processed according to the task processing type of the task to be processed of the service user.
Optionally, the determining, according to the first request message and according to a calculation resource allocation policy for a service user, a task processing type to which a task to be processed of the service user belongs includes: acquiring computing resource data set by a service user who resides in the task scheduling service platform according to the first request message; and determining the task processing type of the task to be processed of the service user according to the computational resource data set by the service user who resides in the task scheduling service platform.
Optionally, the determining, according to computational resource data set by a service user who resides in the task scheduling service platform, a task processing type to which a task to be processed of the service user belongs includes: acquiring the occupation ratio of the computing power resource data set by the service user in the task scheduling service platform according to the computing power resource data set by the service user who resides in the task scheduling service platform; and determining the task processing type of the task to be rendered of the service user according to the occupation ratio corresponding to the computing resource data set by the service user.
Optionally, the obtaining, according to the computing power resource data set by the service user who resides in the task scheduling service platform, the proportion of the computing power resource data set by the service user to the computing power resource data set by all service users in the task scheduling service platform includes: acquiring computing resource data corresponding to each service user residing in the task scheduling service platform; adding and processing the computing resource data corresponding to each service user to obtain total computing resource data set by all service users who reside in the task scheduling service platform; and acquiring the occupation ratio of the computing power resource data set by the service user in the task scheduling service platform to the computing power resource data set by all the service users in the task scheduling service platform according to the ratio of the computing power resource data set by the service user who resides in the task scheduling service platform to the total computing power resource data.
Optionally, the determining, according to the percentage corresponding to the computing resource data set by the service user, the task processing type to which the task to be rendered of the service user belongs includes: sorting according to the proportion corresponding to the computing power resource data set by the service user; determining a service level corresponding to the service user according to the sorting order corresponding to the proportion; and determining the task processing type of the task to be processed of the service user according to the service level corresponding to the service user.
Optionally, the determining, according to the task processing type to which the task to be processed of the service user belongs, a target service user for obtaining the task to be processed includes: determining the execution priority of the tasks to be processed of the service users in the tasks to be processed of all the service users in the task scheduling service platform according to the task processing type to which the tasks to be processed of the service users belong; and determining a target service user for acquiring the tasks to be processed according to the execution priorities of the tasks to be processed of the service users in the tasks to be processed of all the service users in the task scheduling service platform, wherein the execution priority corresponding to the tasks to be processed of the target service user is greater than the execution priorities corresponding to the tasks to be processed of other service users.
Optionally, the determining, according to the execution priorities of the to-be-processed tasks of the service users in the to-be-processed tasks of all service users in the task scheduling service platform, a target service user for obtaining the to-be-processed task, where the execution priority corresponding to the to-be-processed task of the target service user is greater than the execution priorities corresponding to the to-be-processed tasks of other service users, includes: determining an execution sequence corresponding to the tasks to be processed of the service user according to the task processing type to which the tasks to be processed of the service user belong; and determining the execution priority of the tasks to be processed of the service users in the tasks to be processed of all the service users in the task scheduling service platform according to the execution sequence corresponding to the tasks to be processed of the service users.
Optionally, the obtaining the to-be-processed task sent by the user side and returning a first notification message for processing the to-be-processed task to the task processing side includes: acquiring a task to be processed sent by the user side, and acquiring a task processing type to which the task to be processed belongs; and returning a first notification message for processing the task to be processed according to the task processing type to the task processing terminal according to the task processing type to which the task to be processed belongs.
Optionally, the method further includes: determining a charging mode corresponding to the task processing type according to the task processing type of the task to be processed; and performing charging processing on the task to be processed according to the charging mode corresponding to the task processing type.
The embodiment of the present application further provides a task scheduling device, which is applied to a server of a task scheduling service platform, and the device includes: a first request message acquiring unit, configured to acquire a first request message for requesting allocation of a to-be-processed task, where the first request message is sent by a task processing end for processing the task; a second determining unit, configured to determine, according to the first request message and according to a calculation resource allocation policy for a service user, a target service user for acquiring a task to be processed; the sending unit is used for sending a second request message for requesting to acquire the task to be processed to the user side corresponding to the target service user; and the first returning unit is used for acquiring the to-be-processed task sent by the user side and returning a first notification message for processing the to-be-processed task to the task processing side.
The embodiment of the application also provides an electronic device, which comprises a processor and a memory; the memory stores a computer program, and the processor executes the computer program and then executes the method.
An embodiment of the present application further provides a computer storage medium, where a computer program is stored, and the computer program is executed by the processor to perform the method.
Compared with the prior art, the embodiment of the application has the following advantages:
an embodiment of the present application provides a task scheduling system, including: the service end is applied to the task scheduling service platform, and the task processing end is used for processing tasks; the task processing terminal is used for sending a first request message for requesting to distribute the task to be processed to the server terminal; obtaining a first notification message which is returned by the server and used for processing the task to be processed; the server is used for determining a target service user for acquiring the task to be processed according to the first request message and a calculation resource allocation strategy aiming at the service user; sending a second request message for requesting to acquire the task to be processed to a user side corresponding to the target service user; and obtaining the to-be-processed task sent by the user side, and returning a first notification message for processing the to-be-processed task to the task processing side.
In the system, the task processing terminal triggers a request for acquiring the task to be processed, and then determines a target service user for acquiring the task to be processed according to a calculation resource allocation strategy of the service user on the task scheduling service platform, so as to acquire the task to be processed and further allocate the task to be processed to the task processing terminal. The system matches the request message sent by the task processing end with the corresponding to-be-processed task, avoids the excessive to-be-processed tasks from being accumulated on the task scheduling service platform to wait for the task processing end to execute, and improves the processing efficiency of the task processing end for processing the to-be-processed tasks.
Drawings
Fig. 1 is a schematic view of an application scenario of a task scheduling system according to an embodiment of the present application.
Fig. 2 is a logic framework diagram of a task scheduling system according to a first embodiment of the present application.
Fig. 3 is a flowchart of a task scheduling method according to a second embodiment of the present application.
Fig. 4 is a schematic diagram of a task scheduling apparatus according to a third embodiment of the present application.
Fig. 5 is a schematic view of an electronic device provided in a fourth embodiment of the present application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The description used in this application and in the appended claims is for example: "a," "an," "first," and "second," etc., are not necessarily limited to a quantity or order, but rather are used to distinguish one type of information from another.
To facilitate understanding of the systems and methods provided by the embodiments of the present application, prior to describing the embodiments of the present application, a background of the embodiments of the present application is described.
At present, the task scheduling service platform schedules tasks according to the following procedures: and the user side sends a large number of tasks to be processed to the task scheduling service platform to request for processing the tasks to be processed. The task scheduling service platform allocates corresponding loads to the tasks to be processed of a large number of users in a balanced processing mode for processing.
However, in the above method, the task scheduling service platform is a method for allocating a load to a large number of tasks to be processed to process the tasks, which is likely to cause the problem that the tasks to be processed are not processed in time, so that the processing efficiency of the tasks to be processed is low.
For example, in an actual application scenario of view rendering in the home decoration industry, if a task scheduling service platform receives rendering service requests of a large number of users and schedules corresponding loads for tasks to be rendered, one load is easy to be responsible for multiple tasks to be rendered, and therefore the tasks to be rendered are queued, and rendering processing efficiency is low.
Therefore, how to improve the processing efficiency of the task to be processed is a problem to be solved.
In order to solve the above problem, the task scheduling system provided by the present application includes: the service end is applied to the task scheduling service platform and is used for processing the task processing end of the task; the task processing end is used for sending a first request message for requesting to distribute the tasks to be processed to the server end; obtaining a first notification message which is returned by the server and used for processing the task to be processed; the server is used for determining a target service user for acquiring the task to be processed according to the first request message and a calculation resource allocation strategy aiming at the service user; sending a second request message for requesting to acquire the task to be processed to a user side corresponding to the target service user; and obtaining the to-be-processed task sent by the user side, and returning a first notification message for processing the to-be-processed task to the task processing side. According to the task scheduling system, the corresponding to-be-processed task is determined for the task processing end according to the request message of the task processing end and the computing resource allocation strategy, the to-be-processed task is allocated to the task processing end without delay, and the rendering efficiency of the task processing end to the to-be-processed task is improved.
With the above background, those skilled in the art can understand the problems existing in the prior art, and the following provides a detailed description of an application scenario of the rendering task scheduling system of the present application. The task scheduling system provided by the embodiment of the application can be applied to any type of task distribution scene, for example, in the process of rendering a view of a home furnishing scene, the task scheduling and distributing platform schedules and distributes the corresponding task to be rendered for the loader. Specifically, the loader sends a request message for acquiring the tasks to be rendered to a server of the task scheduling and distributing platform, and the server determines the number of the tasks to be rendered according to the request message of the loader. And then, the server determines target service users of the task scheduling platform, which need to acquire the tasks to be rendered, according to the number of the tasks to be rendered, which need to be acquired by the loader, and the computing resource allocation strategy of each service user. The server side obtains a request message of the task to be rendered from a user side corresponding to the target service user, obtains the task to be rendered sent by the user side, and sends the task to be rendered to the load device. The method takes the requirement of the task to be rendered which can be carried by the loader as a starting point, and allocates resources according to the requirement quantity of the task to be rendered of the loader and the computing power required by the task to be rendered of each service user, and obtains the corresponding task to be rendered for the target user. The obtained tasks to be rendered are distributed to the loaders for rendering processing, the phenomenon that the loaders cannot process timely due to the fact that the number of the tasks at the user side is too large is avoided, and the task scheduling and distributing efficiency of the task scheduling and distributing platform for the loaders is improved.
For another example, in the online shopping platform, in order to show a 3D (three-dimensional) shopping scene for a user, a three-dimensional view needs to be constructed for the online store of each merchant, and for a large number of three-dimensional view rendering tasks of multiple merchants, the task scheduling and distributing platform allocates corresponding rendering tasks to the loader as follows. The load device sends a request message for obtaining the task to be rendered to the server side, the server side determines a target merchant needing to obtain the task to be rendered according to the computing power distribution strategy of each merchant, and the request message for obtaining the task to be rendered is sent to the target merchant. And after the service end obtains the task to be rendered sent by the business user end, distributing the task to be rendered to the loader for rendering. By the processing method, the task scheduling and distributing platform distributes the corresponding tasks to be rendered for the loader according to the actual bearable task requirements of the loader, and the task scheduling efficiency of the task scheduling and distributing platform is improved. The method avoids directly receiving a large number of tasks to be rendered at the client side, and distributes one or more rendering tasks for one loader to cause the processing pressure of the loader.
For another example, in a 3D shopping scene, a user is enabled to enjoy an actual shopping scene on a line, and a 3D street view is implemented on the line with an actual street view image. And scheduling and distributing the tasks to be rendered of a plurality of 3D streetscapes to a loader by the following method. And the server side acquires a task to be rendered acquisition request sent by the loader, and determines the type of the task to be rendered which needs to be acquired according to the number of the tasks to be rendered which can be carried by the loader and the calculation power distribution resources required when each 3D street view is rendered. And then, distributing the acquired task to be rendered to a loader for rendering processing.
The task scheduling and distributing platform determines a target user needing to obtain a task to be rendered according to the amount of the task to be rendered which can be carried by the loader and a calculation resource distribution strategy set by the task to be rendered of each user. And then, the server side sends a request message for acquiring the task to be rendered to the target user side, and after the task to be rendered returned by the target user side is acquired, the task to be rendered is distributed to the corresponding loader for rendering.
In addition, the task scheduling system provided by the application can also be applied to other related task scheduling and distributing scenes, and the task scheduling and distributing is carried out according to a large number of to-be-processed tasks and to-be-processed task obtaining requests sent by the loader. And determining a target user for acquiring the tasks to be processed according to the amount of the tasks to be processed which can be borne by the loader and a calculation power resource allocation strategy required by the tasks to be processed of each user. After the server acquires the tasks to be processed from the target users, the tasks are distributed to the loaders, so that the task scheduling and distributing efficiency of the task scheduling and distributing system is improved, and the efficiency of the loaders in processing the tasks to be processed of the users is improved.
First, an application scenario of the task scheduling system according to the embodiment of the present application will be described below.
Fig. 1 is a schematic view of an application scenario of a task scheduling system according to an embodiment of the present application.
As shown in fig. 1, the application scenario includes a server 101 applied to a task scheduling service platform, a task processing terminal 102 for processing tasks, and a client 103.
Taking fig. 1 as an example for detailed description, when the task processing end 102 is currently in a state of being capable of accepting the pending task, a first request message for requesting to allocate the pending task is sent to the server end 101.
After acquiring the first request message, the server 101 first acquires a to-be-processed task from the user terminal 103, and then allocates the to-be-processed task to the task processing terminal 102. Before the task to be processed is acquired from the user side 103, the service user who acquires the task to be processed is determined according to the calculation resource allocation strategy for the service user, and the acquisition is specifically performed by the following method:
acquiring computing resource data set for a service user when the service user is stationed in the task scheduling service platform; determining the proportion of the computing power resource data of each service user in all the computing power resource data of all the service users in the task scheduling service platform according to the computing power resource data corresponding to each service user in the task scheduling service platform; and determining the task processing type of the task to be processed of each service user according to the proportion corresponding to the computing power resource data of each service user.
For example, in an application scenario combining the home decoration scenario, the task scheduling service platform is used to schedule tasks to be rendered of multiple users as an example for explanation:
the service users residing in the task scheduling service platform comprise a first service user A, a second service user B and a third service user C. When the user is parked, the computing power resource data set for the first service user A are 5 computing power resources, the computing power resource data set for the second service user B are 3 computing power resources, and the computing power resource data set for the third service user C are 2 computing power resources.
Therefore, the occupation ratio of the first service user A is larger than that of the second service user B, and the occupation ratio of the second service user B is larger than that of the third service user C.
Therefore, the task to be rendered of the user a is an exclusive rendering task, and the computational power resource required by the task to be rendered of the user a is an exclusive resource, that is, when the task to be rendered of the user a is subjected to rendering processing, a loader that needs to execute the rendering task completely processes the task to be rendered of the user a, and cannot simultaneously process tasks to be rendered of other users.
The task to be rendered of the user B is a cold processing rendering task, that is, a task type which is not frequently occurred belongs to a task type which is occasionally occurred, and the occurrence frequency is low.
The task to be rendered of the user C belongs to the weight sharing task, for example, 3 tasks to be processed rendered by the user C are acquired, the 3 tasks to be processed are allocated to a loader according to a certain weight, and the loader processes the tasks according to the corresponding proportional relationship thereof in sequence.
The above is a detailed description process for determining the task processing type to which the task to be processed of the service user belongs.
In addition, under the condition of determining the task processing type to which the task to be processed of the service user belongs, the target service user for acquiring the task to be processed is determined according to the task processing type. Specifically, according to a task processing type to which a task to be processed of a service user belongs, determining a sequence in which a request sent by a server to a user side corresponding to a target service user requests to acquire the task to be processed.
For example, the task to be rendered of the user a is an exclusive rendering task, and when the loader sends a first request message requesting allocation of the task to be rendered, the server 101 first sends a request message for acquiring the first task to be rendered to a first user corresponding to the user a.
If the first task to be processed fed back by the first user end is not received within the preset time length, it indicates that the user A does not have an exclusive rendering task needing to be processed at this time. The exclusive rendering task means that the task is required to be processed by an independent loader due to large task demand, so as to ensure the real-time performance of the task processing.
Then, the server 101 sends a request message for acquiring a second task to be rendered to a second user corresponding to the user B.
And if the second to-be-rendered task fed back by the second user end is not received within the preset time length, the user B does not have a cold processing rendering task needing to be processed at the moment. The cold processing rendering task refers to a task of partial batch processing or a temporary task, and the occurrence frequency of the task is low.
Finally, if the two types of to-be-processed tasks are not received within the preset time length, the server 101 sends a request message for the user to acquire a third to-be-rendered task to a third user corresponding to the user C. And if the third task to be rendered returned by the third user end is obtained, the third task to be rendered is distributed to the loader, and the loader processes the task to be rendered.
The above description is the description of the task types of the tasks to be rendered for different service users, and the processing priorities of the tasks to be rendered for different service users are determined by different rendering task types. The priority of the three rendering task types described in this example is that the exclusive rendering task takes precedence over the cold processing rendering task, which takes precedence over the weight sharing class task.
An embodiment of the present application provides a task scheduling system, including: the service end is applied to the task scheduling service platform and is used for processing the task processing end of the task; the task processing terminal is used for sending a first request message for requesting to distribute the task to be processed to the server terminal; obtaining a first notification message which is returned by the server and used for processing the task to be processed; the server is used for determining a target service user for acquiring the task to be processed according to the first request message and a calculation power resource allocation strategy aiming at the service user; sending a second request message for requesting to acquire the task to be processed to a user side corresponding to the target service user; and obtaining the to-be-processed task sent by the user side, and returning a first notification message for processing the to-be-processed task to the task processing side.
In the system, the task processing terminal triggers a request for acquiring the task to be processed, and then determines a target service user for acquiring the task to be processed according to a calculation resource allocation strategy of the service user on the task scheduling service platform, so as to acquire the task to be processed and further allocate the task to be processed to the task processing terminal. The system matches the request message sent by the task processing end with the corresponding to-be-processed task, avoids the excessive to-be-processed tasks from being accumulated on the task scheduling service platform to wait for the task processing end to execute, and improves the processing efficiency of the task processing end for processing the to-be-processed tasks.
First embodiment
Fig. 2 is a logic framework diagram of a task scheduling system according to a first embodiment of the present application, and the task scheduling system according to this embodiment is described in detail below with reference to fig. 2.
As shown in fig. 2, the task scheduling system 100 includes: the system comprises a service end 101 applied to a task scheduling service platform and a task processing end 102 used for processing tasks.
The task processing terminal 102 is configured to send a first request message for requesting allocation of a task to be processed to the server terminal; and obtaining a first notification message returned by the server and used for processing the task to be processed. The task processing terminal 102 refers to an actual processing terminal for processing a task, which includes one or more loaders for processing the task. When the load processor can process the next task after completing one task to be processed, a request message for requesting to allocate the task to be processed is sent to the server 101.
Here, the task processing end 102 may refer to a single loader, and for the single loader sending the first request message to the service end 101, the service end 101 receives the first request messages sent by one or more loaders respectively. Then, the server 101 analyzes the user who obtains the to-be-processed task according to the first request message, requests the user to obtain the to-be-processed task, and then allocates the to-be-processed task to the corresponding loader.
Here, the task processing side includes a plurality of loaders for processing tasks; and the task processing end is further configured to, after obtaining the first notification message, allocate a loader corresponding to the to-be-processed task according to the task processing type to which the to-be-processed task belongs, which is included in the first notification message.
The task processing side 102 may collect the request messages of the multiple loaders, and then send a first request message to the service side 101. The server 101 receives a first request message sent by the task processor 102. Then, the server 101 analyzes the user who obtains the to-be-processed task according to the first request message, requests the user to obtain the to-be-processed task, and then allocates the to-be-processed task to the task processing terminal 102, and the task processing terminal 102 allocates the to-be-processed task to the loaders according to the current task execution condition of each loader.
In the embodiment of the application, the task processing terminal 102 triggers to acquire the first request message of the to-be-processed task, and the server 101 matches the to-be-processed task for the task processing terminal according to the first request message, so that the task processing terminal can process the to-be-processed task in time, and the problem that the processing efficiency is reduced due to untimely processing of the to-be-processed task caused by sequencing the to-be-processed tasks according to the to-be-processed task queue under the condition that the server 101 acquires a large number of to-be-processed tasks of users can be avoided.
According to the application scene of the home decoration home furnishing, the loader is currently in a state of being capable of bearing a new task to be rendered, and a first request message for acquiring the task to be rendered is sent to a server side of the task scheduling and distributing platform. The server determines a service user capable of acquiring the task to be rendered, sends a request message for acquiring the task to be rendered to a user side corresponding to the service user, and distributes the acquired task to be rendered to the loader. In the process, the task scheduling and distributing platform acquires the tasks to be rendered from the user side according to the demand of the loader for bearing the rendering tasks and then distributes the tasks to the loader, so that the phenomenon that the tasks to be rendered are not processed timely due to the fact that the task scheduling and distributing platform receives a large number of the tasks to be rendered of the users and cannot distribute the tasks to be rendered to the loader in time is avoided.
The server 101 is configured to determine, according to the first request message and according to a calculation resource allocation policy for a service user, a target service user for acquiring a task to be processed; sending a second request message for requesting to acquire the task to be processed to a user side corresponding to the target service user; and obtaining the to-be-processed task sent by the user side, and returning a first notification message for processing the to-be-processed task to the task processing side.
The server 101 determines a target service user for acquiring the task to be processed according to the computing power resource allocation strategy for the service user. Specifically, the server 101 includes:
a task processing type determining unit, configured to determine, according to the first request message and according to a calculation resource allocation policy for a service user, a task processing type to which a task to be processed of the service user belongs; and the target service user determining unit is used for determining the target service user for acquiring the task to be processed according to the task processing type to which the task to be processed of the service user belongs.
For example, the service users hosted on the task scheduling service platform include a first service user a, a second service user B, and a third service user C. The task processing type to which the task to be rendered of the first service user a belongs is an exclusive rendering task, and the exclusive rendering task is a rendering task with a large demand and needs to be processed by an independent loader so as to ensure the real-time performance of the task processing.
The task processing type to which the task to be rendered of the second service user B belongs is a cold processing rendering task, the cold processing rendering task belongs to a task type which is not frequently occurred, belongs to a task type which occasionally occurs, and the occurrence frequency is low.
And the task processing type to which the task to be rendered of the third service user C belongs is a weight sharing type task. The weight sharing task refers to the task of sharing a load to process the rendering task according to the weight corresponding to each task to be rendered in the plurality of tasks to be rendered. For example, 3 to-be-processed tasks of the C-class rendering are acquired, the 3 to-be-processed tasks are distributed to one loader according to a certain weight, and the loader processes the tasks in sequence according to the corresponding proportional relationship.
Or the task processing end comprises 10 loaders which need to acquire tasks to be distributed, the service user comprises 3 tasks to be processed of C-type rendering, and the tasks to be processed are a fourth task to be rendered E (a task to be rendered belonging to a fourth service user E), a fifth task to be rendered F (a task to be rendered belonging to a fifth service user F), and a sixth task to be rendered G (a task to be rendered belonging to a sixth service user G), respectively.
When the service platform is scheduled by the inbound task, the computational resource weights respectively set by the fourth service user E, the fifth service user F and the sixth service user G are as follows: 1:2:7. the current task processing end comprises 10 active state loaders. The current fourth task e to be rendered, the current fifth task f to be rendered and the current sixth task g to be rendered are the tasks which are being rendered, wherein the task e uses 2 loaders, the average consumed time of the task e is 1 minute, the task f uses 3 loaders, the average consumed time of the task f is 10 minutes, the task g uses 5 loaders, and the average consumed time of the task g is 2 minutes.
At this time, in each assignment proportion of tasks being executed at the task processing end, 7 loaders should be used for the task g, and 5 loaders are actually used, so that the loaders corresponding to the task g cannot separate extra computing power for executing other rendering tasks, and the loaders corresponding to other task ends need to be used. If task e should use 1 loader and 2 loaders, the number of the actual loaders of task e exceeds the number of the standard loaders, and the average processing time of task e is 1 minute and is less than the average processing time of task g by 2 minutes, then task g can be processed from the loaders corresponding to task e by means of redundant force calculation units. In addition, although the actual number of used loaders of task f exceeds the standard number of used loaders, the average processing time of task f is long, and therefore, the loader corresponding to task f rejects the loader borrowing request of task e.
Therefore, when the task to be processed is obtained, the task e and the task g are randomly selected according to the probability, and then the randomly selected task is processed by using the loader.
The task processing type of the task to be processed is illustrated by way of example, where the task processing type determining unit determines the task processing type to which the task to be processed belongs by the following method:
the task processing type determining unit includes:
the first acquisition unit is used for acquiring computing resource data set by a service user who resides in the task scheduling service platform according to the first request message; and the first determining unit is used for determining the task processing type of the task to be processed of the service user according to the computational resource data set by the service user who resides in the task scheduling service platform.
The computing resource data refers to computing resources required when a task to be processed of a service user is processed, where the computing resources may be loaders, and one computing resource corresponds to one loader.
For example, the service users residing in the task scheduling service platform include a first service user a, a second service user B, and a third service user C. When the service user B is resident, the computing power resource data set for the first service user a is 5 computing power resources, the computing power resource data set for the second service user B is 3 computing power resources, and the computing power resource data set for the third service user C is 2 computing power resources.
The task processing type to which the task to be processed of the service user belongs is determined according to computing resource data set by the service user who resides in the task scheduling service platform, and the method specifically comprises the following steps:
the first determination unit includes: the second obtaining unit is used for obtaining the occupation ratio of the computing power resource data set by the service user in the task scheduling service platform to the computing power resource data set by all the service users in the task scheduling service platform according to the computing power resource data set by the service user who resides in the task scheduling service platform; and the first determining subunit is used for determining the task processing type to which the task to be rendered of the service user belongs according to the occupation ratio corresponding to the computing resource data set by the service user.
Wherein, the proportion corresponding to the computing resource data set by the service user is determined by the following mode: the second obtaining unit is specifically configured to obtain computing power resource data corresponding to each service user residing in the task scheduling service platform; adding and processing the computing resource data corresponding to each service user to obtain total computing resource data set by all service users who reside in the task scheduling service platform; and acquiring the occupation ratio of the computing power resource data set by the service user in the task scheduling service platform to the computing power resource data set by all the service users in the task scheduling service platform according to the ratio of the computing power resource data set by the service user who resides in the task scheduling service platform to the total computing power resource data.
Specifically, for example, the total computing resources of the service users hosted in the task scheduling service platform include a first service user a, a second service user B, a third service user C, a first service user a, a second service user B, and a third service user C, which are 10 computing resources. The ratio of the computing power resource data corresponding to the first service user A to the total computing power resource data is 0.5, the ratio of the computing power resource data corresponding to the second service user B to the total computing power resource data is 0.3, and the ratio of the computing power resource data corresponding to the third service user C to the total computing power resource data is 0.2.
After the proportion corresponding to the computing resource data corresponding to the task to be processed of each service user is obtained, determining the task processing type to which the task to be processed of the service user belongs through the following method:
the first determining subunit is specifically configured to perform ranking according to a proportion corresponding to the computing power resource data set by the service user; determining a service level corresponding to the service user according to the sorting order corresponding to the percentage; and determining the task processing type of the task to be processed of the service user according to the service level corresponding to the service user.
The order of the sort results from big to small in the above example is: a first service user A, a second service user B and a third service user C.
Therefore, the service grades corresponding to the service users are in the following sequence from high to low: a first service user A, a second service user B and a third service user C.
Therefore, the task processing type to which the to-be-processed task of the first service user a belongs is an exclusive rendering task. And the task processing type to which the task to be processed of the second service user B belongs is a cold processing rendering task. And the task processing type of the task to be processed of the third service user C is a weight sharing task.
The target service user determining unit determines the target service user for acquiring the task to be processed in the following way:
the execution priority determining unit is used for determining the execution priority of the to-be-processed tasks of the service users in the to-be-processed tasks of all the service users in the task scheduling service platform according to the task processing type to which the to-be-processed tasks of the service users belong; and the target service user determining subunit is used for determining the target service user for acquiring the task to be processed according to the execution priority of the task to be processed of the service user in the task scheduling service platform in the tasks to be processed of all the service users, wherein the execution priority corresponding to the task to be processed of the target service user is greater than the execution priority corresponding to the task to be processed of other service users.
Continuing to use the above example, when determining the service user acquiring the task to be processed, the server performs the process according to the execution priority order of the exclusive rendering task, the cold processing rendering task, and the weight sharing task. That is, first, a first task to be rendered is obtained from a first service user a, if the first service user a does not have the first task to be rendered that needs rendering processing at this time, then a second task to be rendered is obtained from a second service user B, and if the second service user B does not have the second task to be rendered that needs rendering processing at this time, then a third task to be rendered is obtained from a third service user C.
If the first service user a, the second service user B, and the third service user C all have tasks to be rendered that need to perform rendering processing, the target rendering service user obtained by the service end 101 is the first service user a.
The target service user determining subunit is specifically configured to determine, according to a task processing type to which a task to be processed of the service user belongs, an execution sequence corresponding to the task to be processed of the service user; and determining the execution priority of the tasks to be processed of the service users in the tasks to be processed of all the service users in the task scheduling service platform according to the execution sequence corresponding to the tasks to be processed of the service users.
Because the execution priorities of the first service user a, the second service user B and the third service user C are as follows: the first service user a is larger than the second service user B, which is larger than the third service user C.
The server side comprises: a task processing type obtaining unit, configured to obtain a to-be-processed task sent by the user side, and obtain a task processing type to which the to-be-processed task belongs; and the first notification message returning unit is used for returning a first notification message for processing the task to be processed according to the task processing type to the task processing end according to the task processing type to which the task to be processed belongs.
After the task processing end processes the task to be processed, the system further needs to perform charging processing on the task to be processed, and the method specifically includes:
the charging processing unit is used for determining a charging mode corresponding to the task processing type according to the task processing type to which the task to be processed belongs; and performing charging processing on the task to be processed according to the charging mode corresponding to the task processing type.
An embodiment of the present application provides a task scheduling system, including: the service end is applied to the task scheduling service platform and is used for processing the task processing end of the task; the task processing terminal is used for sending a first request message for requesting to distribute the task to be processed to the server terminal; obtaining a first notification message which is returned by the server and used for processing the task to be processed; the server is used for determining a target service user for acquiring the task to be processed according to the first request message and a calculation power resource allocation strategy aiming at the service user; sending a second request message for requesting to acquire the task to be processed to a user side corresponding to the target service user; and obtaining the to-be-processed task sent by the user side, and returning a first notification message for processing the to-be-processed task to the task processing side.
In the system, the task processing terminal triggers a request for acquiring the task to be processed, and then determines a target service user for acquiring the task to be processed according to a calculation resource allocation strategy of the service user on the task scheduling service platform, so as to acquire the task to be processed and further allocate the task to be processed to the task processing terminal. The system matches the request message sent by the task processing end with the corresponding to-be-processed task, avoids the excessive to-be-processed tasks from being accumulated on the task scheduling service platform to wait for the task processing end to execute, and improves the processing efficiency of the task processing end for processing the to-be-processed tasks.
Second embodiment
Corresponding to the application scenario embodiment of the task scheduling system and the task scheduling system provided in the first embodiment, a second embodiment of the present application provides a task scheduling method. Fig. 3 is a flowchart of a task scheduling method according to a second embodiment of the present application, and the method according to the present embodiment is described below with reference to fig. 3.
The following description refers to embodiments for the purpose of illustrating the principles of the methods, and is not intended to be limiting in actual use.
As shown in fig. 3, in step S301, a first request message for requesting allocation of a task to be processed, which is sent by a task processing end for processing the task, is acquired.
The step is used for acquiring a first request message which is sent by the task processing end and used for requesting to distribute the tasks to be processed, and the task processing end triggers the acquisition request. And then the server side determines a target service user needing to acquire the task to be processed according to the trigger request by the following method, so as to acquire the task to be processed and distribute the task to be processed for the task processing side.
Compared with the prior art, the method has the advantages that the user side sends a large number of tasks to be processed to the task scheduling service platform, and the task processing end is allocated for the tasks to be processed.
As shown in fig. 3, in step S302, according to the first request message, a target service user for acquiring a task to be processed is determined according to a calculation resource allocation policy for the service user.
The step is used for determining the service user for acquiring the task to be processed, and then acquiring the task to be processed from the user side corresponding to the service user on the basis.
The service user for acquiring the task to be processed is determined by the following method:
the determining, according to the first request message and according to a calculation resource allocation policy for a service user, a target service user for acquiring a task to be processed includes:
according to the first request message and a calculation resource allocation strategy aiming at a service user, determining a task processing type to which a task to be processed of the service user belongs; and determining a target service user for acquiring the task to be processed according to the task processing type of the task to be processed of the service user.
Wherein, the task processing type to which the task to be processed of the target service user belongs is determined by the following method:
the determining, according to the first request message and according to a calculation resource allocation policy for a service user, a target service user for acquiring a task to be processed includes: according to the first request message and a calculation resource allocation strategy aiming at a service user, determining a task processing type to which a task to be processed of the service user belongs; and determining a target service user for acquiring the task to be processed according to the task processing type of the task to be processed of the service user.
Specifically, the determining, according to the first request message and according to a calculation resource allocation policy for a service user, a task processing type to which a task to be processed of the service user belongs includes:
acquiring computing resource data set by a service user who resides in the task scheduling service platform according to the first request message; and determining the task processing type of the task to be processed of the service user according to the computing resource data set by the service user who resides in the task scheduling service platform.
Here, the determining, according to computing resource data set by a service user who resides in the task scheduling service platform, a task processing type to which a task to be processed of the service user belongs includes:
acquiring the occupation ratio of the computing power resource data set by the service user in the task scheduling service platform according to the computing power resource data set by the service user who resides in the task scheduling service platform; and determining the task processing type of the task to be rendered of the service user according to the occupation ratio corresponding to the computing resource data set by the service user.
The method for acquiring the occupation ratio of the computing power resource data set by the service user in the task scheduling service platform according to the computing power resource data set by the service user who resides in the task scheduling service platform comprises the following steps:
acquiring computing power resource data corresponding to each service user who resides in the task scheduling service platform; adding and processing the computing resource data corresponding to each service user to obtain total computing resource data set by all service users who reside in the task scheduling service platform; and acquiring the ratio of the computing power resource data set by the service user in the task scheduling service platform to the computing power resource data set by all service users in the task scheduling service platform according to the ratio of the computing power resource data set by the service user who resides in the task scheduling service platform to the total computing power resource data.
The above is a specific detailed description for determining the task processing type to which the task to be processed of the service user belongs. In addition, after the task processing type is obtained, the target service user for obtaining the task to be processed is determined by the following method:
the determining the target service user for acquiring the task to be processed according to the task processing type to which the task to be processed of the service user belongs comprises the following steps:
determining the execution priority of the to-be-processed tasks of the service users in the to-be-processed tasks of all service users in the task scheduling service platform according to the task processing type to which the to-be-processed tasks of the service users belong; and determining a target service user for acquiring the tasks to be processed according to the execution priorities of the tasks to be processed of the service users in the tasks to be processed of all the service users in the task scheduling service platform, wherein the execution priority corresponding to the tasks to be processed of the target service user is greater than the execution priorities corresponding to the tasks to be processed of other service users.
The determining, according to the execution priorities of the to-be-processed tasks of the service users in the to-be-processed tasks of all the service users in the task scheduling service platform, a target service user for obtaining the to-be-processed task, where the execution priority corresponding to the to-be-processed task of the target service user is greater than the execution priorities corresponding to the to-be-processed tasks of other service users, includes:
determining an execution sequence corresponding to the tasks to be processed of the service user according to the task processing type to which the tasks to be processed of the service user belong; and determining the execution priority of the tasks to be processed of the service users in the tasks to be processed of all the service users in the task scheduling service platform according to the execution sequence corresponding to the tasks to be processed of the service users.
The above is a specific detail explanation for determining the target service user for acquiring the task to be processed. The above is similar to the corresponding parts of the scene embodiment and the first embodiment, and reference may be made to the scene embodiment and the first embodiment for the relevant points.
As shown in fig. 3, in step S303, a second request message for requesting to acquire the to-be-processed task is sent to the user side corresponding to the target service user.
The step is used for acquiring the task to be processed, and specifically, the server sends an acquisition request to the client, and the client returns the task to be processed.
As shown in fig. 3, in step S304, a to-be-processed task sent by the user end is obtained, and a first notification message for processing the to-be-processed task is returned to the task processing end.
The obtaining of the to-be-processed task sent by the user side and returning of the first notification message for processing the to-be-processed task to the task processing side include:
acquiring a task to be processed sent by the user side, and acquiring a task processing type to which the task to be processed belongs; and returning a first notification message for processing the task to be processed according to the task processing type to the task processing terminal according to the task processing type to which the task to be processed belongs.
In addition, the method further comprises the following steps:
determining a charging mode corresponding to the task processing type according to the task processing type of the task to be processed; and carrying out charging processing on the task to be processed according to the charging mode corresponding to the task processing type.
Third embodiment
Corresponding to the application scenario embodiment of the task scheduling system and the task scheduling method provided in the second embodiment, a third embodiment of the present application provides a task scheduling device. Fig. 4 is a schematic diagram of a task scheduling apparatus according to a third embodiment of the present application, and the apparatus according to the present embodiment is described below with reference to fig. 4.
The following description refers to embodiments for the purpose of illustrating the principles of the methods, and is not intended to be limiting in actual use.
The task scheduling apparatus shown in fig. 4 is applied to a server of a task scheduling service platform, and the apparatus includes:
a first request message acquiring unit 401, configured to acquire a first request message for requesting to allocate a to-be-processed task, where the first request message is sent by a task processing end for processing the task;
a second determining unit 402, configured to determine, according to the first request message and according to a calculation resource allocation policy for a service user, a target service user for acquiring a task to be processed;
a sending unit 403, configured to send a second request message for requesting to acquire a to-be-processed task to a user side corresponding to the target service user;
a first returning unit 404, configured to obtain a to-be-processed task sent by the user side, and return a first notification message for processing the to-be-processed task to the task processing side.
Fourth embodiment
Corresponding to the method of the second embodiment of the present application, a fourth embodiment of the present application further provides an electronic device. As shown in fig. 5, fig. 5 is a schematic view of an electronic device provided in a fourth embodiment of the present application. The electronic device includes: at least one processor 501, at least one communication interface 502, at least one memory 503, and at least one communication bus 504; optionally, the communication interface 502 may be an interface of a communication module, such as an interface of a GSM module; the processor 501 may be a processor CPU, or an Application Specific Integrated Circuit ASIC (Application Specific Integrated Circuit), or one or more Integrated circuits configured to implement embodiments of the present invention. The memory 503 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory. Wherein, the memory 503 stores programs, and the processor 501 calls the programs stored in the memory 503 to execute the method of the second embodiment of the present invention.
Fifth embodiment
A fifth embodiment of the present application also provides a computer storage medium corresponding to the method of the second embodiment of the present application. The computer storage medium stores a computer program that is executed by a processor to perform the method of the second embodiment.
Although the present application has been described with reference to the preferred embodiments, it is not intended to limit the present application, and those skilled in the art can make variations and modifications without departing from the spirit and scope of the present application, therefore, the scope of the present application should be determined by the appended claims.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory. The memory may include forms of volatile memory in a computer readable medium, random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
1. Computer-readable media, including both permanent and non-permanent, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. As defined herein, computer readable Media does not include non-Transitory computer readable Media (transient Media), such as modulated data signals and carrier waves.
2. As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Claims (24)

1. A task scheduling system, comprising: the service end is applied to the task scheduling service platform, and the task processing end is used for processing tasks;
the task processing terminal is used for sending a first request message for requesting to distribute the task to be processed to the server terminal; obtaining a first notification message which is returned by the server and used for processing the task to be processed;
the server is used for determining a target service user for acquiring the task to be processed according to the first request message and a calculation power resource allocation strategy aiming at the service user; sending a second request message for requesting to acquire the task to be processed to a user side corresponding to the target service user; and a to-be-processed task sent by the user side is obtained, and a first notification message for processing the to-be-processed task is returned to the task processing side.
2. The system of claim 1, wherein the server comprises:
a task processing type determining unit, configured to determine, according to the first request message and according to a calculation resource allocation policy for a service user, a task processing type to which a task to be processed of the service user belongs;
and the target service user determining unit is used for determining the target service user for acquiring the task to be processed according to the task processing type to which the task to be processed of the service user belongs.
3. The system according to claim 2, wherein the task processing type determination unit includes:
the first acquisition unit is used for acquiring computing resource data set by a service user who resides in the task scheduling service platform according to the first request message;
and the first determining unit is used for determining the task processing type of the task to be processed of the service user according to the computing resource data set by the service user who resides in the task scheduling service platform.
4. The system of claim 3, wherein the first determining unit comprises:
the second obtaining unit is used for obtaining the occupation ratio of the computing power resource data set by the service user in the task scheduling service platform to the computing power resource data set by all the service users in the task scheduling service platform according to the computing power resource data set by the service user who resides in the task scheduling service platform;
and the first determining subunit is used for determining the task processing type of the task to be rendered of the service user according to the proportion corresponding to the computing power resource data set by the service user.
5. The system according to claim 4, wherein the second obtaining unit is specifically configured to obtain computing power resource data corresponding to each service user residing in the task scheduling service platform; adding and processing the computing resource data corresponding to each service user to obtain total computing resource data set by all service users who reside in the task scheduling service platform; and acquiring the ratio of the computing power resource data set by the service user in the task scheduling service platform to the computing power resource data set by all service users in the task scheduling service platform according to the ratio of the computing power resource data set by the service user who resides in the task scheduling service platform to the total computing power resource data.
6. The system according to claim 4, wherein the first determining subunit is specifically configured to perform sorting according to a proportion corresponding to the computing power resource data set by the service user; determining a service level corresponding to the service user according to the sorting order corresponding to the percentage; and determining the task processing type of the task to be processed of the service user according to the service level corresponding to the service user.
7. The system of claim 2, wherein the target serving subscriber determining unit comprises:
the execution priority determining unit is used for determining the execution priority of the to-be-processed tasks of the service users in the to-be-processed tasks of all the service users in the task scheduling service platform according to the task processing type to which the to-be-processed tasks of the service users belong;
and the target service user determining subunit is used for determining the target service user for acquiring the to-be-processed task according to the execution priority of the to-be-processed task of the service user in the to-be-processed tasks of all service users in the task scheduling service platform, wherein the execution priority corresponding to the to-be-processed task of the target service user is greater than the execution priority corresponding to the to-be-processed tasks of other service users.
8. The system according to claim 7, wherein the target service user determining subunit is specifically configured to determine, according to a task processing type to which a task to be processed of the service user belongs, an execution order corresponding to the task to be processed of the service user; and determining the execution priority of the tasks to be processed of the service users in the tasks to be processed of all the service users in the task scheduling service platform according to the execution sequence corresponding to the tasks to be processed of the service users.
9. The system of claim 1, wherein the server comprises:
a task processing type obtaining unit, configured to obtain a to-be-processed task sent by the user side, and obtain a task processing type to which the to-be-processed task belongs;
and the first notification message returning unit is used for returning a first notification message for processing the task to be processed according to the task processing type to the task processing end according to the task processing type to which the task to be processed belongs.
10. The system of claim 9, further comprising:
the charging processing unit is used for determining a charging mode corresponding to the task processing type according to the task processing type to which the task to be processed belongs; and performing charging processing on the task to be processed according to the charging mode corresponding to the task processing type.
11. The system of claim 1, wherein the task processing side comprises a plurality of loaders for executing processing services by users;
and the task processing end is further configured to, after obtaining the first notification message, allocate a loader corresponding to the to-be-processed task according to the task processing type to which the to-be-processed task belongs, which is included in the first notification message.
12. A task scheduling method is applied to a server side of a task scheduling service platform, and comprises the following steps:
acquiring a first request message which is sent by a task processing end for processing a task and used for requesting to distribute a task to be processed;
determining a target service user for acquiring the task to be processed according to the first request message and a calculation resource allocation strategy aiming at the service user;
sending a second request message for requesting to acquire the task to be processed to a user side corresponding to the target service user;
and a to-be-processed task sent by the user side is obtained, and a first notification message for processing the to-be-processed task is returned to the task processing side.
13. The method of claim 12, wherein determining a target service subscriber for obtaining the pending task according to the first request message and a power resource allocation policy for the service subscriber comprises:
according to the first request message and a calculation resource allocation strategy aiming at a service user, determining a task processing type to which a task to be processed of the service user belongs;
and determining a target service user for acquiring the task to be processed according to the task processing type of the task to be processed of the service user.
14. The method according to claim 13, wherein the determining, according to the first request message and according to the computing resource allocation policy for the service user, the task processing type to which the task to be processed of the service user belongs comprises:
acquiring computing resource data set by a service user who resides in the task scheduling service platform according to the first request message;
and determining the task processing type of the task to be processed of the service user according to the computational resource data set by the service user who resides in the task scheduling service platform.
15. The method according to claim 14, wherein the determining a task processing type to which a task to be processed of a service user belongs according to computational resource data set by the service user who hosts the task scheduling service platform comprises:
acquiring the occupation ratio of the calculation resource data set by the service user in the task scheduling service platform to the calculation resource data set by all service users in the task scheduling service platform according to the calculation resource data set by the service user who resides in the task scheduling service platform;
and determining the task processing type of the task to be rendered of the service user according to the occupation ratio corresponding to the computing resource data set by the service user.
16. The method according to claim 15, wherein the obtaining, according to the computing power resource data set by the service user who is resident in the task scheduling service platform, the proportion of the computing power resource data set by the service user to the computing power resource data set by all service users in the task scheduling service platform comprises:
acquiring computing power resource data corresponding to each service user who resides in the task scheduling service platform;
adding and processing the computing power resource data corresponding to each service user to obtain total computing power resource data set by all service users who reside in the task scheduling service platform;
and acquiring the ratio of the computing power resource data set by the service user in the task scheduling service platform to the computing power resource data set by all service users in the task scheduling service platform according to the ratio of the computing power resource data set by the service user who resides in the task scheduling service platform to the total computing power resource data.
17. The method according to claim 15, wherein the determining a task processing type to which the task to be rendered of the service user belongs according to a proportion corresponding to the computing power resource data set by the service user comprises:
sorting according to the proportion corresponding to the computing power resource data set by the service user;
determining a service level corresponding to the service user according to the sorting order corresponding to the percentage;
and determining the task processing type of the task to be processed of the service user according to the service level corresponding to the service user.
18. The method according to claim 13, wherein the determining, according to the task processing type to which the task to be processed of the service user belongs, a target service user for obtaining the task to be processed includes:
determining the execution priority of the tasks to be processed of the service users in the tasks to be processed of all the service users in the task scheduling service platform according to the task processing type to which the tasks to be processed of the service users belong;
and determining a target service user for acquiring the tasks to be processed according to the execution priorities of the tasks to be processed of the service users in the tasks to be processed of all the service users in the task scheduling service platform, wherein the execution priority corresponding to the tasks to be processed of the target service user is greater than the execution priorities corresponding to the tasks to be processed of other service users.
19. The method according to claim 18, wherein the determining, according to the execution priorities of the to-be-processed tasks of the service users in the to-be-processed tasks of all service users in the task scheduling service platform, a target service user for obtaining the to-be-processed task, where the execution priority corresponding to the to-be-processed task of the target service user is greater than the execution priorities corresponding to the to-be-processed tasks of other service users, includes:
determining an execution sequence corresponding to the tasks to be processed of the service user according to the task processing type to which the tasks to be processed of the service user belong;
and determining the execution priority of the tasks to be processed of the service users in the tasks to be processed of all the service users in the task scheduling service platform according to the execution sequence corresponding to the tasks to be processed of the service users.
20. The method according to claim 12, wherein the obtaining the to-be-processed task sent by the user side and returning a first notification message for processing the to-be-processed task to the task processing side includes:
acquiring a task to be processed sent by the user side, and acquiring a task processing type to which the task to be processed belongs;
and returning a first notification message for processing the task to be processed according to the task processing type to the task processing terminal according to the task processing type to which the task to be processed belongs.
21. The method of claim 20, further comprising:
determining a charging mode corresponding to the task processing type according to the task processing type of the task to be processed;
and performing charging processing on the task to be processed according to the charging mode corresponding to the task processing type.
22. A task scheduling device is applied to a server of a task scheduling service platform, and comprises:
a first request message acquiring unit, configured to acquire a first request message for requesting to allocate a to-be-processed task, where the first request message is sent by a task processing end for processing the task;
a second determining unit, configured to determine, according to the first request message and according to a calculation power resource allocation policy for a service user, a target service user for acquiring a task to be processed;
the sending unit is used for sending a second request message for requesting to acquire the task to be processed to the user side corresponding to the target service user;
and the first returning unit is used for acquiring the to-be-processed task sent by the user side and returning a first notification message for processing the to-be-processed task to the task processing side.
23. An electronic device, comprising a processor and a memory;
the memory has a computer program stored therein, which when executed by the processor performs the method of any one of claims 12-21.
24. A computer storage medium, characterized in that it stores a computer program which, when executed by a processor, performs the method of any one of claims 12-21.
CN202211490481.XA 2022-11-25 2022-11-25 Task scheduling system, method and device and electronic equipment Active CN115586957B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211490481.XA CN115586957B (en) 2022-11-25 2022-11-25 Task scheduling system, method and device and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211490481.XA CN115586957B (en) 2022-11-25 2022-11-25 Task scheduling system, method and device and electronic equipment

Publications (2)

Publication Number Publication Date
CN115586957A true CN115586957A (en) 2023-01-10
CN115586957B CN115586957B (en) 2023-04-14

Family

ID=84783597

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211490481.XA Active CN115586957B (en) 2022-11-25 2022-11-25 Task scheduling system, method and device and electronic equipment

Country Status (1)

Country Link
CN (1) CN115586957B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105373429A (en) * 2014-08-20 2016-03-02 腾讯科技（深圳）有限公司 Task scheduling method, device and system
US9898347B1 (en) * 2017-03-15 2018-02-20 Sap Se Scaling computing resources in a cluster
CN111654542A (en) * 2020-06-03 2020-09-11 支付宝(杭州)信息技术有限公司 Proxy server, execution server, reception device, and task execution method
CN112882940A (en) * 2021-03-01 2021-06-01 深圳前海微众银行股份有限公司 Use case task scheduling method, system, device, equipment and storage medium
CN113343148A (en) * 2021-06-18 2021-09-03 上海哔哩哔哩科技有限公司 Resource processing method, client, server and system
CN113687932A (en) * 2021-08-30 2021-11-23 上海商汤科技开发有限公司 Task scheduling method, device and system, electronic equipment and storage medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105373429A (en) * 2014-08-20 2016-03-02 腾讯科技（深圳）有限公司 Task scheduling method, device and system
US9898347B1 (en) * 2017-03-15 2018-02-20 Sap Se Scaling computing resources in a cluster
CN111654542A (en) * 2020-06-03 2020-09-11 支付宝(杭州)信息技术有限公司 Proxy server, execution server, reception device, and task execution method
CN112882940A (en) * 2021-03-01 2021-06-01 深圳前海微众银行股份有限公司 Use case task scheduling method, system, device, equipment and storage medium
CN113343148A (en) * 2021-06-18 2021-09-03 上海哔哩哔哩科技有限公司 Resource processing method, client, server and system
CN113687932A (en) * 2021-08-30 2021-11-23 上海商汤科技开发有限公司 Task scheduling method, device and system, electronic equipment and storage medium

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
GUANG-XU QIN等: "Design of Workflow Working Time Server Supporting Highly Concurrent Request", 《2009 WRI WORLD CONGRESS ON SOFTWARE ENGINEERING》 *
晋文明等: "大规模负载生成客户端影响因素研究", 《计算机与现代化》 *
王波: "基于工控机的高效液相色谱电子医疗系统研究与设计", 《中国优秀硕士学位论文全文数据库 工程科技Ⅱ辑》 *

Also Published As

Publication number Publication date
CN115586957B (en) 2023-04-14

Similar Documents

Publication Publication Date Title
CN112269641B (en) Scheduling method, scheduling device, electronic equipment and storage medium
CN105007337A (en) Cluster system load balancing method and system thereof
CN105373429A (en) Task scheduling method, device and system
CN107832143B (en) Method and device for processing physical machine resources
EP3293969A1 (en) Method of terminal-based conference load-balancing, and device and system utilizing same
CN106294472A (en) The querying method of a kind of Hadoop data base HBase and device
CN106897299B (en) Database access method and device
JPWO2018220708A1 (en) Resource allocation system, management device, method and program
CN113127170A (en) Method, system, and article of manufacture for pairing in a contact center system
CN112888005A (en) MEC-oriented distributed service scheduling method
CN106775975B (en) Process scheduling method and device
CN114116173A (en) Method, device and system for dynamically adjusting task allocation
CN114036031A (en) Scheduling system and method for resource service application in enterprise digital middleboxes
CN116069493A (en) Data processing method, device, equipment and readable storage medium
CN115586957B (en) Task scheduling system, method and device and electronic equipment
CN110096352A (en) Process management method, device and computer readable storage medium
CN116226178A (en) Data query method and device, storage medium and electronic device
CN115904729A (en) Method, device, system, equipment and medium for connection allocation
CN109903023B (en) Resource allocation method and system
CN115914236B (en) Storage space allocation adjustment method and device, electronic equipment and storage medium
CN114979411B (en) Distributed image processing method, device, equipment and system
CN116431327B (en) Task current limiting processing method and fort machine
CN117785486A (en) Environment resource allocation method, device, equipment and medium
CN111754332B (en) Service request processing method and device, storage medium and electronic equipment
CN117357886A (en) Cloud game resource management method, system, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant