CN102508716B - Task control device and task control method - Google Patents
Task control device and task control method Download PDFInfo
- Publication number
- CN102508716B CN102508716B CN201110300153.4A CN201110300153A CN102508716B CN 102508716 B CN102508716 B CN 102508716B CN 201110300153 A CN201110300153 A CN 201110300153A CN 102508716 B CN102508716 B CN 102508716B
- Authority
- CN
- China
- Prior art keywords
- task
- queue
- dependence
- perform
- tasks
- 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.)
- Active
Links
Abstract
The invention provides a task control device and a task control method. The task control device comprises a task classification module and a task execution module, wherein the task classification module is used for classifying tasks to be executed into independent tasks and tasks with a dependence relation; and the task execution module is used for executing the independent tasks and classifying the tasks with the dependence relation into one or more task queues according to the dependence relation between the tasks, and executing the tasks in each task queue according to the dependence relation between the tasks in each task queue. According to the invention, the tasks are classified and the execution way of the tasks is determined according to the classification result, so that the tasks can be smoothly executed and the execution efficiency is ensured.
Description
Technical field
The present invention relates to field of computer technology, in particular to a kind of task control device and a kind of task control method.
Background technology
All can use the device performing and manage asynchronous task in general enterprises application and other various signal conditioning packages, asynchronous task refers in application system according to one section of specific business processing program of specifying scheduling scheme to perform.Execution and managerial demand management devices of these asynchronous task manage and arrange.
Task apparatus in more existing application systems, the general mode of all adopting serial and performing, cannot many queues concurrence performance, or use the thread of given number, form a thread pool, adopt the mechanism such as I/O completing port, multi-thread concurrent Processing tasks, from waiting task, task is taken out one by one, the mode performed one by one in each thread.
And in actual applications, there is certain relation between multiple pending task, there is strict sequencing in some, the execution of a rear task depends on the execution result of previous or multiple task, therefore need to perform in sequence, cannot simply adopt multi-thread concurrent to perform; Then there is not precedence relationship in some pending task, as long as perform just passable, can adopt the mode of grouping concurrence performance, the demand in this actual scene, existing system and device cannot meet.
Therefore, need a kind of device for task management newly, can carry out grouping management to task, concurrence performance and the order of carrying out task respectively perform, and promote the efficiency of tasks carrying.
Summary of the invention
Problem to be solved by this invention is, provides a kind of device for task management newly, can carry out grouping management to task, and concurrence performance and the order of carrying out task respectively perform, and promote the efficiency of tasks carrying.
In view of this, the invention provides a kind of task control device, comprising: classification of task module, is independent task and the task with dependence by pending task division; Task execution module, perform described independent task, and according to dependence each other, by the described task division with dependence in one or more task queue, and according to the dependence between the task in each task queue, perform the task in described each task queue in order.By this technical scheme, task is divided, and decide the executive mode of task according to division result, both ensured that task can perform smoothly, in turn ensure that the efficiency of execution.
In technique scheme, preferably, described task execution module, when being in the arbitrary tasks carrying mistake in task queue, according to the parameter preset, judges whether to continue to perform other tasks in same task queue.By this technical scheme, can freely control to have in the task of dependence, task action result be on the impact of follow-up work.
In technique scheme, preferably, also comprise: hang up control module, when executing the task pending operation, for described independent task, when described independent task such as is at the pending state, allow to perform pending operation, for the task with dependence, according to described parameter, judge described there is the tasks carrying mistake of dependence after whether continue to perform other tasks in same queue, and when judged result is for being, allow to perform pending operation, when judged result is no, forbid performing pending operation.By this technical scheme, ensure that the smooth execution that task suspension operates.
In technique scheme, preferably, described task execution module also records the execution result of the task in described each task queue; Described task control device also comprises: repeat control module, execute the task repeat operation time, judge whether the execution result that there is task to be repeated, and only when judged result is for being, for described independent task, perform described independent task, for the task with dependence, according to other tasks in same queue whether still in commission, and when judged result is for being, forbid the task described in repeating with dependence, when judged result is no, restart to perform the task in described same queue.By this technical scheme, the task of ensure that can repeat smoothly.
In technique scheme, preferably, described task execution module, according to presetting to the priority of described independent task and/or serial number, performs described independent task in order.By this technical scheme, when resource-constrained, can, to the execution reasonably controlling independent task, ensure to there will not be blocking or other mistakes.
The present invention also provides a kind of task control method, comprising: step 202, is independent task and the task with dependence by pending task division; Step 204, performs described independent task; Step 206, according to dependence each other, by the described task division with dependence in one or more task queue, and according to the dependence between the task in each task queue, performs the task in described each task queue in order.By this technical scheme, task is divided, and decide the executive mode of task according to division result, both ensured that task can perform smoothly, in turn ensure that the efficiency of execution.
In technique scheme, preferably, described step 206 also comprises: when being in the arbitrary tasks carrying mistake in task queue, according to the parameter preset, judges whether to continue to perform other tasks in same task queue.By this technical scheme, can freely control to have in the task of dependence, task action result be on the impact of follow-up work.
In technique scheme, preferably, also comprise: when executing the task pending operation, for described independent task, when described independent task such as is at the pending state, allow to perform pending operation, for the task with dependence, according to described parameter, judge described there is the tasks carrying mistake of dependence after whether continue to perform other tasks in same queue, and when judged result is for being, allow to perform pending operation, when judged result is no, forbid performing pending operation.By this technical scheme, ensure that the smooth execution that task suspension operates.
In technique scheme, preferably, described step 206 also comprises: the execution result recording the task in described each task queue; Task control method also comprises: execute the task repeat operation time, judge whether the execution result that there is task to be repeated, and only when judged result is for being, for described independent task, perform described independent task, for the task with dependence, according to other tasks in same queue whether still in commission, and when judged result is for being, forbid the task described in repeating with dependence, when judged result is no, restart to perform the task in described same queue.By this technical scheme, the task of ensure that can repeat smoothly.
In technique scheme, preferably, described step 204 specifically comprises: according to presetting to the priority of described independent task and/or serial number, perform described independent task in order.By this technical scheme, when resource-constrained, can, to the execution reasonably controlling independent task, ensure to there will not be blocking or other mistakes.
By above technical scheme, a kind of task control device and a kind of task control method can be realized, by arranging the relation between pending asynchronous task, reach optimization, efficiently, correctly, tasks carrying mode flexibly, and achieve the management function of multiple asynchronous task, according to the priority dependence between task, improve the efficiency that asynchronous task performs, meet multiple-task and perform demand and the management and control demand to tasks carrying.
Accompanying drawing explanation
Fig. 1 is the block diagram of task control device according to an embodiment of the invention;
Fig. 2 is the process flow diagram of task control method according to an embodiment of the invention;
Fig. 3 is the workflow diagram of task control device according to an embodiment of the invention;
Fig. 4 is the workflow diagram of task control device according to an embodiment of the invention;
Fig. 5 is the workflow diagram of task control device according to an embodiment of the invention;
Fig. 6 is the workflow diagram of task control device according to an embodiment of the invention;
Fig. 7 is the task state transition schematic diagram of task control device according to an embodiment of the invention;
Fig. 8 is the interface sectional drawing of task control device according to an embodiment of the invention;
Fig. 9 is the interface sectional drawing of task control device according to an embodiment of the invention.
Embodiment
In order to more clearly understand above-mentioned purpose of the present invention, feature and advantage, below in conjunction with the drawings and specific embodiments, the present invention is further described in detail.
Set forth a lot of detail in the following description so that fully understand the present invention, but the present invention can also adopt other to be different from other modes described here and implement, and therefore, the present invention is not limited to the restriction of following public specific embodiment.
Fig. 1 is the block diagram of task control device according to an embodiment of the invention.
As shown in Figure 1, the invention provides a kind of task control device 100, comprising: classification of task module 102, is independent task and the task with dependence by pending task division; Task execution module 104, perform described independent task, and according to dependence each other, by the described task division with dependence in one or more task queue, and according to the dependence between the task in each task queue, perform the task in described each task queue in order.By this technical scheme, task is divided, and decide the executive mode of task according to division result, both ensured that task can perform smoothly, in turn ensure that the efficiency of execution.
In technique scheme, described task execution module 104, when being in the arbitrary tasks carrying mistake in task queue, according to the parameter preset, judges whether to continue to perform other tasks in same task queue.By this technical scheme, can freely control to have in the task of dependence, task action result be on the impact of follow-up work.
In technique scheme, also comprise: hang up control module 106, when executing the task pending operation, for described independent task, when described independent task such as is at the pending state, allow to perform pending operation, for the task with dependence, according to described parameter, judge described there is the tasks carrying mistake of dependence after whether continue to perform other tasks in same queue, and when judged result is for being, allow to perform pending operation, when judged result is no, forbid performing pending operation.By this technical scheme, ensure that the smooth execution that task suspension operates.
In technique scheme, described task execution module 104 also records the execution result of the task in described each task queue; Described task control device also comprises: repeat control module 108, execute the task repeat operation time, judge whether the execution result that there is task to be repeated, and only when judged result is for being, for described independent task, perform described independent task, for the task with dependence, according to other tasks in same queue whether still in commission, and when judged result is for being, forbid the task described in repeating with dependence, when judged result is no, restart to perform the task in described same queue.By this technical scheme, the task of ensure that can repeat smoothly.
In technique scheme, described task execution module 104, according to presetting to the priority of described independent task and/or serial number, performs described independent task in order.By this technical scheme, when resource-constrained, can, to the execution reasonably controlling independent task, ensure to there will not be blocking or other mistakes.
Fig. 2 is the process flow diagram of task control method according to an embodiment of the invention.
As shown in Figure 2, the present invention also provides a kind of task control method, comprising: step 202, is independent task and the task with dependence by pending task division; Step 204, performs described independent task; Step 206, according to dependence each other, by the described task division with dependence in one or more task queue, and according to the dependence between the task in each task queue, performs the task in described each task queue in order.By this technical scheme, task is divided, and decide the executive mode of task according to division result, both ensured that task can perform smoothly, in turn ensure that the efficiency of execution.
In technique scheme, described step 206 also comprises: when being in the arbitrary tasks carrying mistake in task queue, according to the parameter preset, judges whether to continue to perform other tasks in same task queue.By this technical scheme, can freely control to have in the task of dependence, task action result be on the impact of follow-up work.
In technique scheme, also comprise: when executing the task pending operation, for described independent task, when described independent task such as is at the pending state, allow to perform pending operation, for the task with dependence, according to described parameter, judge described there is the tasks carrying mistake of dependence after whether continue to perform other tasks in same queue, and when judged result is for being, allow to perform pending operation, when judged result is no, forbid performing pending operation.By this technical scheme, ensure that the smooth execution that task suspension operates.
In technique scheme, described step 206 also comprises: the execution result recording the task in described each task queue; Task control method also comprises: execute the task repeat operation time, judge whether the execution result that there is task to be repeated, and only when judged result is for being, for described independent task, perform described independent task, for the task with dependence, according to other tasks in same queue whether still in commission, and when judged result is for being, forbid the task described in repeating with dependence, when judged result is no, restart to perform the task in described same queue.By this technical scheme, the task of ensure that can repeat smoothly.
In technique scheme, described step 204 specifically comprises: according to presetting to the priority of described independent task and/or serial number, perform described independent task in order.By this technical scheme, when resource-constrained, can, to the execution reasonably controlling independent task, ensure to there will not be blocking or other mistakes.
Below the principle of the task control device in embodiments of the invention is described.
1) rule of task call:
What be submitted to the task object needs realization unification in the task control device of the present embodiment calls Standard Interface, and interface is described below:
As long as realize the object of this interface like this, all can be submitted in the task control device of the present embodiment, task need to be performed time, as long as to call Do method according to this interface specification just passable for the task control device of the present embodiment.
Task object adopts Binary Serialization mode task object serializing to be stored in database.
During tasks carrying, then unserializing mode is adopted to be loaded in internal memory by task object, according to the Do method of the interface of interface specification calling task object.
Below the explanation of serializing/unserializing:
Serializing: convert the object in calculator memory to text or binary data stores for data.
Unserializing: text on storage medium or binary message are converted to the object in calculator memory.
2) the contextual storage of task object:
The information of some system environmentss when context of task object is job invocation and data, such as submitter, submission time, current system operator etc., environmental context is imported into, the Binary Serialization sequence of algorithms of employing standard is in database, adopt scale-of-two unserializing algorithm to load object during tasks carrying again, rewrite context object.
3) task object is submitted to the interface (CreateTask method) of task control device:
This interface is called by task control device user of service:
Import into: task object,
Context object,
Task is encoded,
Task names,
Whether queue,
The task that this task relies on,
Classification of task,
Whether queue execution error continues,
Queue mission failure is attempted performing number of times,
Executed number of times,
Whether task can repeat,
This interface regulation specification of job invocation to task control device.
4) for task object provides corresponding state:
Task object comprises following several state: unsettled, etc. pending, perform in, terminate, hang up.
Unsettled: to represent task record and to be just submitted in device and to be persisted to database.
Etc. pending: after environmental test, task status to become etc. pending.
In execution: expression task have invoked manner of execution by according to interface specification, but is not also finished.
Terminate/complete: expression task is finished.
Hang up: expression task is not wanted to be performed, but performs possibly later, perform and hang up action.(can activate after hang-up, after activating, state is etc. pending).
5) rule of the execution sequencing of queue task:
<1>: task to be submitted in task control device and to be persisted in the task list of database, according to the mode of maximum serial number+1, stored in serial number.Namely the mode of+1 is adopted to provide serial number.
According to task whether queue, whether Existence dependency relationship, set up corresponding tasks carrying queue, will the task of dependence be had to be included into different queues, do not have the task of dependence according to task priority, from thread pool, distribute thread resources perform and there is no the task of dependence.
<2>: in task control device, state is that the task of " completing " and " hang-up " all can not perform in queue.
State is only had to be that the task of " waiting pending " just can perform in queue.
6) rule having the task of dependence and do not have the setting of the task (independent task) relied on and task queue to create:
There is the task of dependence (queue task): the multiple task of having relation of interdependence, create an independent task queue, these tasks are put in this queue and perform, according to dependence sequence, be not performed by the priority of task relied on;
There is no the task (independently non-queue task) relied on: represent that execution and other task have nothing to do, according to the priority of these independent tasks, from available thread pool, distribute independent thread resources concurrence performance, little and priority the is high task of serial number is first performed.
7) execution result of task performs impact to queue:
If task is set to queue execution error whether continue=True, represent that in queue, current task performs unsuccessfully, the follow-up work in queue continues to perform.
Whether queue execution error continues=False, represents that in queue, current task performs unsuccessfully, and this queue suspends the follow-up work performed in queue and do not continue to perform.
Parameter by importing in job invocation interface: whether queue execution error continues the tasks carrying situation controlling queue.
8) task suspension and activation rule:
The hang-up of independent task non-queue task: just can hang up when task status to be only etc. pending, after hanging up, task can not perform, and task status can activate after hanging up is etc. pending after activation.
Have the hang-up of the queue task of dependence: when whether queue execution error continues=True, just can hang up queue task, and task status to be only etc. pending.Queue task after hang-up no longer performs; Can activate after hang-up, be etc. pending after activation.If whether queue execution error continues=False, the task in queue cannot be hung up.
9) setting that can repeat and executing rule:
Repeating of independent task: when tasks carrying is crossed (namely execution result has record), just can repeat, by repeating function, task performs again.
There is repeating of the queue task of dependence: cross (namely execution result has record) when tasks carrying and just can repeat by repeating function, the queue of this task will perform again, and queue will be executed the task according to Cahn-Ingold-Prelog sequence rule (minimum serial number is preferential).
10) queue mission failure can perform number of times rule:
Queue mission failure can be attempted performing number of times: have failed if show that queue type task performs, can continue the number of times attempting performing.
Executed number of times: after recording the failure of current queue type tasks carrying, the number of times repeated.
If do not limit execution number of times: queue mission failure can perform number of times and be set to 0, executed number of times is set to-1.Each tasks carrying is complete, and no matter failed or successful, executed number of times increases by 1.
The condition of demand fulfillment of again executing the task is: queue mission failure can perform number of times-executed number of times > 0, if no longer meet this condition, this task is no longer re-executed by trial.
11) data structure of task object and task action result is described below:
Task and task action result are 1 many-many relationship:
The data structure of task object:
| Field name | Remarks |
| Task is encoded | Character string |
| Task names | Character string |
| Task status | Enumerate: unsettled, etc. pending, perform in, terminate, hang up |
| Whether queue | Boolean (true: table is queue, false: table is not queue) |
| Task queue classification | Character string |
| Whether queue execution error continues | Boolean (true: show passable, false: table cannot) |
| Task object | Binary object |
| Tasks carrying context | Binary object |
| Queue mission failure can be attempted performing number of times | Integer (0 represents not limited number of times) |
| Executed number of times | Integer (-1 represents not limited number of times) |
| Task can repeat | Boolean (true: show passable, false: table cannot) |
| Serial number | Lint-long integer |
The data structure of task action result:
| Field name | Remarks |
| Task ID | The unique identification of task |
| The tasks carrying start time | Date-time |
| The tasks carrying end time | Date-time |
| Whether tasks carrying is successful | Boolean (true: telogenesis merit, false: show unsuccessful) |
| Tasks carrying abnormal information | Character string |
12) the execution flow process of task control device is described below:
As shown in Figure 3, the execution flow process of task is described:
Step 302, carries out the establishment of calling task by job creator;
Step 304, when after a job invocation to task control device, can check its legitimacy;
Step 306, according to characteristics such as the dependences of task, can determine that task is the task of needing to perform in queue or perform separately after checking;
Step 308 is executed the task separately then according to the priority of performing separately of task, and the available resources in existing thread pool, these independent tasks of concurrent execution;
Step 310, if queue task, then according to the dependence of task, find its should belonging to task queue, there is not this queue and then create new queue;
Step 312, sorts the group task by dependence according to dependence and pushes a queue, not by being first performed of relying on;
Step 314, executes the task;
Step 316, after tasks carrying terminates, determines whether queue task, and the independent task of non-queue has directly been set to;
Step 318, the task of queue then will judge its execution result and attribute further;
Step 320, if run succeeded, then performs the next task in queue;
Step 322, if perform failure, then determines whether continuing to attempt according to performing the configuration unsuccessfully whether heavily attempting row;
Step 324, if retry after allowing mistake, then attempts performing again, but the number of times attempted is no more than default number of times restriction, if do not allow, then directly terminates this queue.
As shown in Figure 4, the flow process of task suspension is described:
Step 402, is carrying out pending operation to task, is first checking the state of this task, if current state is " waiting pending ", then entering step 406, if current state is not " waiting pending ", then enters step 404;
Step 404, terminates and points out to carry out pending operation;
Step 406, the hang-up of the task of " waiting pending ", needs the attribute judging this task further;
Step 408, if independent not relying on of task, then directly arrange this task status for " hang-up ", this task can not be performed;
Step 410, if being suspended of task is the queue task having dependence, then needs to judge whether this task queue is the queue that mistake can continue to perform further, if so, then enter step 408, hang up this task, if not, enter step 404, point out this generic task to hang up.
As shown in Figure 5, the flow process of mission-enabling is described:
Step 502, when carrying out activation manipulation to task, first checks the state of this task;
Step 504, only has current state to be that the task of " hang-up " just can be activated, and perform after " activations " operate, task status is set to " waiting pending ";
Step 506, if the state of current task is not " hang-up ", then prompting can not activate.
As shown in Figure 6, the flow process that task re-executes is described:
Step 602, in time manually specifying a task to re-execute immediately, first judge whether this task exists execution result, namely judge whether this task performed, the task of there is not execution result cannot re-execute, after needing to wait task scheduling apparatus to perform by original plan, just can perform;
Step 604, if there is execution result, carries out queue judgement;
Step 606, directly re-executes just passable for the independent task without relying on;
Step 608, and for there being the queue task of dependence, judge the operation conditions of the queue residing for this task, if in performing, then can not re-execute, after needing to wait this queue trip to terminate;
Step 610, if the quene state belonging to this task is for being finished, then needing the whole queue restarted residing for this task, re-executing from first task of queue.
As shown in Figure 7, the State Transferring relation of task is described:
Just the task into task control device is submitted to be " opening " state 702, " waiting pending " 704 is become after checking, " wait pending " 704 task can become state for the task of " hang-up " 706 by pending operation, and the task of " hang-up " 706 can become the task of " waiting pending " 704 again by activation manipulation, " wait pending " 704 task be set to " in execution " 708 when starting to perform, after successful execution completes, become " completing " 710 state, if perform unsuccessful, can configure according to user, optionally again be set to " waiting pending " 704, again to attempt performing this task.Task control device provides the interface of monitor task implementation status, as shown in Figure 8, can view the state of task, additionally provide the interface of monitor task result, as shown in Figure 9.
Serializing algorithm/unserializing realizes: employing be that Binary Serialization/unserializing technology of standard realizes.
Serial number+1 realizes: certainly the adding of native system database realizes serial number+1.
In sum, by above technical scheme, can the relation of configuration task flexibly, can define without the self task relied on and have the queue of dependence to execute the task, and the control of implementation and the optimization of execution efficiency of task in device is reached by the attribute of definition task, effectively meet various different demand and scene in real application systems, effectively make use of resource, improve the optimization of the correctness of task, controllability, reliability and tasks carrying efficiency.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (6)
1. a task control device, is characterized in that, comprising:
Pending task division is independent task and the task with dependence by classification of task module;
Task execution module, perform described independent task, and according to dependence each other, by the described task division with dependence in one or more task queue, and according to the dependence between the task in each task queue, perform the task in described each task queue in order;
Wherein, described task execution module, when being in the arbitrary tasks carrying mistake in task queue, according to the parameter preset, judges whether to continue to perform other tasks in same task queue;
Hang up control module, when executing the task pending operation, for described independent task, when described independent task such as is at the pending state, allow to perform pending operation, for the task with dependence, according to described parameter, judge described there is the tasks carrying mistake of dependence after whether continue to perform other tasks in same queue, and when judged result is for being, allow to perform pending operation, when judged result is no, forbid performing pending operation.
2. task control device according to claim 1, is characterized in that, described task execution module also records the execution result of the task in described each task queue;
Described task control device also comprises:
Repeat control module, execute the task repeat operation time, judge whether the execution result that there is task to be repeated, and only when judged result is for being, for described independent task, perform described independent task, for the described task with dependence, judge whether still in commission other tasks in same queue, and when judged result is for being, forbid the task described in repeating with dependence, when judged result is no, restart to perform the task in described same queue.
3. task control device according to claim 1 and 2, is characterized in that, described task execution module, according to presetting to the priority of described independent task and/or serial number, performs described independent task in order.
4. a task control method, is characterized in that, comprising:
Pending task division is independent task and the task with dependence by step 202;
Step 204, performs described independent task;
Step 206, according to dependence each other, by the described task division with dependence in one or more task queue, and according to the dependence between the task in each task queue, performs the task in described each task queue in order; And
When being in the arbitrary tasks carrying mistake in task queue, according to the parameter preset, judge whether to continue to perform other tasks in same task queue;
When executing the task pending operation, for described independent task, when described independent task such as is at the pending state, allow to perform pending operation,
For the task with dependence, according to described parameter, judge described there is the tasks carrying mistake of dependence after whether continue to perform other tasks in same queue, and when judged result is for being, allow to perform pending operation, when judged result is no, forbid performing pending operation.
5. task control method according to claim 4, is characterized in that, described step 206 also comprises:
Record the execution result of the task in described each task queue;
Described task control method also comprises:
Execute the task repeat operation time, judge whether the execution result that there is task to be repeated, and only when judged result is for being,
For described independent task, perform described independent task,
For the described task with dependence, judge whether still in commission other tasks in same queue, and when judged result is for being, forbid the task described in repeating with dependence, when judged result is no, restart to perform the task in described same queue.
6. the task control method according to claim 4 or 5, is characterized in that, described step 204 specifically comprises:
According to presetting to the priority of described independent task and/or serial number, perform described independent task in order.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110300153.4A CN102508716B (en) | 2011-09-29 | 2011-09-29 | Task control device and task control method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110300153.4A CN102508716B (en) | 2011-09-29 | 2011-09-29 | Task control device and task control method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102508716A CN102508716A (en) | 2012-06-20 |
| CN102508716B true CN102508716B (en) | 2015-04-15 |
Family
ID=46220808
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110300153.4A Active CN102508716B (en) | 2011-09-29 | 2011-09-29 | Task control device and task control method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102508716B (en) |
Families Citing this family (38)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103077083A (en) * | 2013-01-09 | 2013-05-01 | 苏州亿倍信息技术有限公司 | Method and system for processing tasks |
| CN104182295B (en) * | 2013-05-27 | 2018-11-02 | 阿里巴巴集团控股有限公司 | A kind of data back up method and device |
| CN103279385A (en) * | 2013-06-01 | 2013-09-04 | 北京华胜天成科技股份有限公司 | Method and system for scheduling cluster tasks in cloud computing environment |
| CN104778074B (en) * | 2014-01-14 | 2019-02-26 | 腾讯科技（深圳）有限公司 | A kind of calculating task processing method and processing device |
| CN104461502A (en) * | 2014-11-03 | 2015-03-25 | 广州汇讯营销咨询有限公司 | Task management method and system based on Hadoop |
| CN104484167B (en) * | 2014-12-05 | 2018-03-09 | 广州华多网络科技有限公司 | Task processing method and device |
| CN104463482A (en) * | 2014-12-16 | 2015-03-25 | 用友软件股份有限公司 | Task allocation method and task allocation device |
| CN105068912B (en) * | 2015-07-29 | 2020-05-01 | 北京京东尚科信息技术有限公司 | Method and device for executing webpage task |
| CN105389207A (en) * | 2015-11-06 | 2016-03-09 | 成都视达科信息技术有限公司 | Adaptive data request processing method and apparatus, task scheduler and adaptive data request processing system |
| CN105389209B (en) * | 2015-12-25 | 2019-04-26 | 中国建设银行股份有限公司 | A kind of asynchronous batch tasks processing method and system |
| CN105677331A (en) * | 2015-12-30 | 2016-06-15 | 浙江大华系统工程有限公司 | Task execution method and device |
| CN107015820A (en) * | 2016-01-27 | 2017-08-04 | 阿里巴巴集团控股有限公司 | Using startup method, device and server |
| CN105653365A (en) * | 2016-02-22 | 2016-06-08 | 青岛海尔智能家电科技有限公司 | Task processing method and device |
| US10261830B2 (en) * | 2016-06-14 | 2019-04-16 | Microsoft Technology Licensing, Llc | Cross-device task execution |
| CN107544886A (en) * | 2016-06-27 | 2018-01-05 | 上海中兴软件有限责任公司 | A kind of block process dispatching method and device |
| CN108021431B (en) * | 2016-11-04 | 2022-02-11 | 广东亿迅科技有限公司 | Web data interaction based Hive management method and system |
| WO2018120171A1 (en) | 2016-12-30 | 2018-07-05 | 华为技术有限公司 | Method, device and system for executing stored procedure |
| CN108509257B (en) * | 2017-02-28 | 2022-07-22 | 苏宁易购集团股份有限公司 | Message processing method and device based on multithreading |
| CN107193659A (en) * | 2017-05-24 | 2017-09-22 | 千寻位置网络有限公司 | The system and design method of upkeep operation task |
| CN107239334B (en) * | 2017-05-31 | 2019-03-12 | 清华大学无锡应用技术研究院 | Handle the method and device irregularly applied |
| CN107682389B (en) * | 2017-07-24 | 2020-02-14 | 平安科技（深圳）有限公司 | Method, terminal and computer readable storage medium for executing network request |
| CN107633080B (en) * | 2017-09-25 | 2020-06-23 | 联想(北京)有限公司 | User task processing method and device |
| CN107818016A (en) * | 2017-11-22 | 2018-03-20 | 苏州麦迪斯顿医疗科技股份有限公司 | Server application design method, request event processing method and processing device |
| CN109725994B (en) * | 2018-06-15 | 2024-02-06 | 中国平安人寿保险股份有限公司 | Method and device for executing data extraction task, terminal and readable storage medium |
| CN109725995B (en) * | 2018-06-15 | 2024-04-12 | 中国平安人寿保险股份有限公司 | Method, device and equipment for executing data extraction task and readable storage medium |
| CN109447411A (en) * | 2018-09-26 | 2019-03-08 | 平安普惠企业管理有限公司 | Business Process Control method, apparatus, computer equipment and storage medium |
| CN109492019B (en) * | 2018-10-16 | 2024-03-08 | 平安科技（深圳）有限公司 | Service request response method, device, computer equipment and storage medium |
| CN109445929A (en) * | 2018-11-16 | 2019-03-08 | 杭州数澜科技有限公司 | A kind of method and system of scheduler task |
| CN110096346B (en) * | 2019-03-29 | 2021-06-15 | 广州思德医疗科技有限公司 | Multi-computing-node training task processing method and device |
| CN111176819B (en) * | 2019-12-31 | 2021-07-09 | 苏州长光华医生物医学工程有限公司 | Sample test pipeline task scheduling method, system and computer storage medium |
| CN111580939B (en) * | 2020-04-01 | 2023-09-01 | 微梦创科网络科技（中国）有限公司 | Method and device for processing transactions in hierarchical and asynchronous mode |
| CN113534750B (en) * | 2020-04-15 | 2022-12-02 | 北京旷视机器人技术有限公司 | Job scheduling method, device, system, equipment and medium under intensive storage |
| CN112000682A (en) * | 2020-08-25 | 2020-11-27 | 北京达佳互联信息技术有限公司 | Data synchronization task scheduling method, device, server and storage medium |
| CN112559156A (en) * | 2020-12-23 | 2021-03-26 | 百果园技术(新加坡)有限公司 | Multi-dependency task grouping management method, device, equipment and storage medium |
| CN112349361B (en) * | 2021-01-08 | 2021-05-04 | 浙江太美医疗科技股份有限公司 | Execution scheduling method, system and readable medium for clinical trial data processing task |
| CN112965794B (en) * | 2021-02-19 | 2024-03-22 | 西安智周深鉴信息科技集团有限公司 | Algorithm calling method, electronic equipment and storage medium |
| CN112988362B (en) * | 2021-05-14 | 2022-12-30 | 南京蓝洋智能科技有限公司 | Task processing method and device, electronic equipment and storage medium |
| CN114021507B (en) * | 2022-01-06 | 2022-04-29 | 苏州贝克微电子股份有限公司 | Automatic integrated circuit parallel simulation method |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1818868A (en) * | 2006-03-10 | 2006-08-16 | 浙江大学 | Multi-task parallel starting optimization of built-in operation system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7243351B2 (en) * | 2002-12-17 | 2007-07-10 | International Business Machines Corporation | System and method for task scheduling based upon the classification value and probability |
| CN100476739C (en) * | 2007-08-23 | 2009-04-08 | 南京联创科技股份有限公司 | Method for managing group task |
| CN101470626A (en) * | 2007-12-27 | 2009-07-01 | 新奥特（北京）视频技术有限公司 | Task ranking method |
| JP5259714B2 (en) * | 2008-06-30 | 2013-08-07 | パナソニック株式会社 | Execution order determination apparatus, execution order determination program, execution order determination circuit, and information processing apparatus |
| CN101510164B (en) * | 2009-03-25 | 2013-05-22 | 北京中星微电子有限公司 | Multi-service scheduling method, apparatus and system |
-
2011
- 2011-09-29 CN CN201110300153.4A patent/CN102508716B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1818868A (en) * | 2006-03-10 | 2006-08-16 | 浙江大学 | Multi-task parallel starting optimization of built-in operation system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102508716A (en) | 2012-06-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102508716B (en) | Task control device and task control method | |
| CN106802826B (en) | Service processing method and device based on thread pool | |
| US8516492B2 (en) | Soft partitions and load balancing | |
| CN101201753B (en) | Method for configuring and managing multimode machine supervising engine | |
| US7441240B2 (en) | Process scheduling apparatus, process scheduling method, program for process scheduling, and storage medium recording a program for process scheduling | |
| CN105159768A (en) | Task management method and cloud data center management platform | |
| TW200401529A (en) | System and method for the allocation of grid computing workload to network workstations | |
| CN101135981A (en) | Method and device for realizing batch report generation | |
| CN110737534A (en) | Task processing method and device and server | |
| WO2016112625A1 (en) | System realizing script operation in preset embedded system | |
| CN110162344B (en) | Isolation current limiting method and device, computer equipment and readable storage medium | |
| CN110427257A (en) | Multi-task scheduling method, device and computer readable storage medium | |
| CN107861715B (en) | Service establishing system and method | |
| US20140136570A1 (en) | Controller and program | |
| CN105808346A (en) | Task scheduling method and device | |
| CN110708197B (en) | Monitoring device, method for setting monitoring policy of monitoring device, and storage medium | |
| CN102455932B (en) | Serial execution method, device and system for task instances | |
| CN111371848A (en) | Request processing method, device, equipment and storage medium | |
| CN113157411A (en) | Reliable configurable task system and device based on Celery | |
| CN109002286A (en) | Data asynchronous processing method and device based on synchronous programming | |
| US11301792B2 (en) | Cross domain integration in product lifecycle management | |
| CN109034668B (en) | ETL task scheduling method, ETL task scheduling device, computer equipment and storage medium | |
| CN115981826A (en) | Task scheduling processing method and device, computer equipment and readable storage medium | |
| CN109040491A (en) | On-hook behavior processing method, device, computer equipment and storage medium | |
| US20230393782A1 (en) | Io request pipeline processing device, method and system, and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20160202 Address after: 100094 Beijing City, North Road, Haidian District, No. 68, building 2, floor 2 Patentee after: You Pu Information Technology Co., Ltd of UFSOFT Address before: 100094 Beijing city Haidian District North Road No. 68, UFIDA Software Park Patentee before: UFIDA Software Co., Ltd. |