CN105159768A - Task management method and cloud data center management platform - Google Patents
Task management method and cloud data center management platform Download PDFInfo
- Publication number
- CN105159768A CN105159768A CN201510570007.1A CN201510570007A CN105159768A CN 105159768 A CN105159768 A CN 105159768A CN 201510570007 A CN201510570007 A CN 201510570007A CN 105159768 A CN105159768 A CN 105159768A
- Authority
- CN
- China
- Prior art keywords
- thread
- task
- pond
- goal task
- goal
- 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.)
- Pending
Links
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a task management method and a cloud data center management platform. The method comprises the following steps: applying to a business layer of the cloud data center management platform, and independently aiming at each functional module in the cloud data center management platform to create at least one thread pool. The method also comprises the following steps: S1: obtaining a target task which aims at a target functional module; S2: judging whether the thread pool which aims at the target task is in the presence or not, scheduling the target task to the thread pool corresponding to the target task to execute the target task if the thread pool which aims at the target task is in the presence, and executing an S3 if the thread pool which aims at the target task is in the absence; S3: further judging whether the thread pool corresponding to a type to which the target task belongs is in the presence or not, scheduling the target task to the thread pool corresponding to the type to which the target task belongs to execute the target task if the thread pool corresponding to the type to which the target task belongs is in the presence, and executing an S4 if the thread pool corresponding to the type to which the target task belongs is in the absence; and S4: scheduling the target task to be executed in a main thread pool. According to the scheme, task execution latency time can be shortened, and user experience is improved.
Description
Technical field
The present invention relates to field of computer technology, particularly a kind of task management method and cloud data center management platform.
Background technology
Along with the develop rapidly of computer technology, cloud computing progressively becomes the focus point of industry, each large enterprises have added the research field of cloud computing, and multiple fields such as science, culture, education, health, government, ecommerce, high-performance calculation, Internet of Things of being put into by cloud computing service use.
At present, this task, by creating thread pool, ensureing when receiving task, distributing in this thread pool and performing by cloud data center management platform.
But, there are some tasks not high for the requirement of real-time when performing, but it is consuming time longer when performing, such as, create virtual machine, delete virtual machine, restart virtual machine, New-deployed Network etc., only after these tasks carryings terminate, namely can continue to perform other follow-up tasks when thread pool is idle, and follow-up required these other tasks performed may there are certain requirements real-time tool, thus cause the task of requirement real-time to be delayed, affect Consumer's Experience.
Summary of the invention
In view of this, the invention provides a kind of task management method and cloud data center management platform, with improve have a task of requirement to real-time be performed efficiency, improve Consumer's Experience.
The invention provides a kind of task management method based on cloud data center management platform, be applied to the operation layer of described cloud data center management platform, the construction strategy of described operation layer according to pre-configured thread pool and the property parameters of thread pool, respectively for each functional module in cloud data center management platform, create the thread pool of at least one, wherein, at least one thread pool created for same functional module comprises main thread pond; Also comprise:
S1: obtain the goal task for objective function module;
S2: judge whether to exist to should the thread pool of goal task, if exist, dispatches to performing in the thread pool of goal task by goal task; If do not exist, perform S3;
S3: judge whether to exist to should the thread pool of type belonging to goal task further, if exist, dispatches to performing in the thread pool of type belonging to goal task by this goal task; If do not exist, perform S4;
S4: this goal task is dispatched and performs in main thread pond.
Preferably, described scheduling by goal task performs in any one subject thread pond, comprising:
Judge whether comprise idle thread in this subject thread pond, if comprise idle thread, utilize this idle thread to perform described goal task; If do not comprise idle thread, continue to perform next step;
Judge that the Thread Count and first in this subject thread pond presets the relation that thread numerical value, second presets thread numerical value; Wherein, the described first default thread numerical value is less than the described second default thread numerical value;
When Thread Count in this subject thread pond is less than the described first default thread numerical value, newly-built thread in this subject thread pond, and utilize goal task described in this newly-built thread execution;
When Thread Count in this subject thread pond is not less than the described first default thread numerical value, and when being less than the described second default thread numerical value, judge whether buffer queue comprises buffer further, if comprise, described goal task is put into described buffer queue, to make in this subject thread pond, when comprising idle thread, to utilize idle thread to perform described goal task; If do not comprise, then newly-built thread in this subject thread pond, and utilize goal task described in this newly-built thread execution;
When Thread Count in this subject thread pond equals the described second default thread numerical value, refuse the process to described goal task.
Preferably, described described goal task is put into described buffer queue, comprising:
Determine the execution priority of described goal task, and according to the execution priority of the described goal task determined, described goal task is put into described buffer queue, arranges according to execution priority order from small to large to direction of popping from stacked to make putting into rear described buffer queue.
Preferably, comprise further:
When any one subject thread pond comprises idle thread, and when this idle thread is not assigned to required performing of task in setting-up time section, then destroy this idle thread.
Preferably,
Comprise further: goal task is being dispatched in any one subject thread pond in the process performed, record task main information and task events information that described goal task is performed, and the task main information of record and task events information are stored in database;
Wherein, described task main information comprises: at least one in the title of the unique identification of task, task names, affiliated functional module, executing state, task body, task creation time, job end time, task action result, implementation progress; Described task events information comprises: task is performed the mark of each key point performed in process, the unique identification of task and task is performed to the explanation of each key point performed in process;
Comprise further: in cloud data center, management platform is interrupted, and after cloud data center management platform is restarted, according to task main information and the task events information of each task stored in database, the unclosed task of execution is loaded in its respective thread pond and continues to perform.
Present invention also offers a kind of cloud data center management platform, comprising:
Dispensing unit, for the construction strategy of thread pool that configures and the property parameters of thread pool;
Thread pool creating unit, for respectively for each functional module in cloud data center management platform, creates the thread pool of at least one, and wherein, at least one thread pool created for same functional module comprises main thread pond;
Acquiring unit, for obtaining the goal task for objective function module;
First judging unit, for judging whether to exist to should the thread pool of goal task, if existing, triggering scheduling unit and being dispatched by goal task to performing in the thread pool of goal task; If do not exist, trigger the second judging unit and perform corresponding operating;
Second judging unit, for judging whether to exist to should the thread pool of type belonging to goal task, if existing, triggering scheduling unit and being dispatched by this goal task to performing in the thread pool of type belonging to goal task; If do not exist, this goal task is dispatched and is performed in main thread pond by triggering scheduling unit.
Preferably, described scheduling unit, for judging whether comprise idle thread in this subject thread pond, if comprise idle thread, utilizes this idle thread to perform described goal task; If do not comprise idle thread, continue to judge that the Thread Count and first in this subject thread pond presets the relation that thread numerical value, second presets thread numerical value; Wherein, the described first default thread numerical value is less than the described second default thread numerical value;
When Thread Count in this subject thread pond is less than the described first default thread numerical value, newly-built thread in this subject thread pond, and utilize goal task described in this newly-built thread execution;
When Thread Count in this subject thread pond is not less than the described first default thread numerical value, and when being less than the described second default thread numerical value, judge whether buffer queue comprises buffer further, if comprise, described goal task is put into described buffer queue, to make in this subject thread pond, when comprising idle thread, to utilize idle thread to perform described goal task; If do not comprise, then newly-built thread in this subject thread pond, and utilize goal task described in this newly-built thread execution;
When Thread Count in this subject thread pond equals the described second default thread numerical value, refuse the process to described goal task.
Preferably, described scheduling unit, for determining the execution priority of described goal task, and according to the execution priority of the described goal task determined, described goal task is put into described buffer queue, arranges according to execution priority order from small to large to direction of popping from stacked to make putting into rear described buffer queue.
Preferably, comprise further: idle thread destroys unit, for when any one subject thread pond comprises idle thread, and when this idle thread is not assigned to required performing of task in setting-up time section, then destroy this idle thread.
Preferably,
Comprise further: record cell, for goal task being dispatched in any one subject thread pond in the process performed, record task main information and task events information that described goal task is performed, and the task main information of record and task events information are stored in database;
Wherein, described task main information comprises: at least one in the title of the unique identification of task, task names, affiliated functional module, executing state, task body, task creation time, job end time, task action result, implementation progress; Described task events information comprises: task is performed the mark of each key point performed in process, the unique identification of task and task is performed to the explanation of each key point performed in process;
Comprise further: recovery unit, for interrupting in cloud data center management platform, and after cloud data center management platform is restarted, according to task main information and the task events information of each task stored in database, recover to perform unclosed task, to trigger scheduling unit, unclosed for execution task is loaded into continuation execution in its respective thread pond.
Embodiments provide a kind of task management method and cloud data center management platform, by respectively for each functional module in cloud data center management platform, create at least one thread pool, to ensure when getting the goal task for objective function module, if at least one thread pool created comprise to should goal task thread pool or comprise should the thread pool of type belonging to goal task, then this goal task can be dispatched and perform in its respective thread pond, owing to being for each functional module creates at least one thread pool, this at least one thread pool created only performs the task of the corresponding function module, thus the stand-by period of tasks carrying can be reduced, improve Consumer's Experience.
Accompanying drawing explanation
Fig. 1 is the method flow diagram that the embodiment of the present invention provides;
Fig. 2 is the level Organization Chart of cloud data center of the present invention management platform;
Fig. 3 is the other method process flow diagram that the embodiment of the present invention provides;
Fig. 4 is the method flow diagram that thread pool that the embodiment of the present invention provides is executed the task;
Fig. 5 is the cloud data center management platform structural drawing that the embodiment of the present invention provides;
Fig. 6 is another structural drawing of the cloud data center management platform that the embodiment of the present invention provides.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described.Obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
As shown in Figure 1, embodiments provide a kind of task management method based on cloud data center management platform, be applied to the operation layer of cloud data center management platform, the construction strategy of operation layer according to pre-configured thread pool and the property parameters of thread pool, respectively for each functional module in cloud data center management platform, create the thread pool of at least one, wherein, at least one thread pool created for same functional module comprises main thread pond; The method can comprise the following steps:
Step 101: obtain the goal task for objective function module.
Step 102: judge whether to exist to should the thread pool of goal task, if exist, dispatches to performing in the thread pool of goal task by goal task; If do not exist, perform step 103.
Step 103: judge whether to exist to should the thread pool of type belonging to goal task further, if exist, dispatches to performing in the thread pool of type belonging to goal task by this goal task; If do not exist, perform step 104.
Step 104: this goal task is dispatched and performs in main thread pond.
According to this programme, by respectively for each functional module in cloud data center management platform, create at least one thread pool, to ensure when getting the goal task for objective function module, if at least one thread pool created comprise to should goal task thread pool or comprise should the thread pool of type belonging to goal task, then this goal task can be dispatched and perform in its respective thread pond, owing to being for each functional module creates at least one thread pool, this at least one thread pool created only performs the task of the corresponding function module, thus the stand-by period of tasks carrying can be reduced, improve Consumer's Experience.
Not infinitely-great for Thread Count included in the thread pool created, in a preferred embodiment of the invention, the first default thread numerical value and second can be utilized to preset thread numerical value limit the Thread Count in thread pool, wherein, first presets thread numerical value is less than the second default thread numerical value, goal task is dispatched and performs in any one subject thread pond, comprise: judge whether comprise idle thread in this subject thread pond, if comprise idle thread, utilize this idle thread performance objective task; If do not comprise idle thread, continue to perform next step;
Judge that the Thread Count and first in this subject thread pond presets the relation that thread numerical value, second presets thread numerical value; Wherein, the first default thread numerical value is less than the second default thread numerical value;
When Thread Count in this subject thread pond is less than the first default thread numerical value, newly-built thread in this subject thread pond, and utilize this newly-built thread execution goal task;
When Thread Count in this subject thread pond is not less than the first default thread numerical value, and when being less than the second default thread numerical value, judge whether buffer queue comprises buffer further, if comprise, goal task is put into buffer queue, to make in this subject thread pond, when comprising idle thread, to utilize idle thread performance objective task; If do not comprise, then newly-built thread in this subject thread pond, and utilize this newly-built thread execution goal task;
When Thread Count in this subject thread pond equals the second default thread numerical value, refuse the process to goal task.
Because some tasks are higher to requirement of real-time, in order to ensure the timely process to these tasks, in a preferred embodiment of the invention, goal task is put into buffer queue, comprise: the execution priority determining goal task, and according to the execution priority of the goal task determined, goal task is put into buffer queue, arrange according to execution priority order from small to large to direction of popping from stacked to make putting into rear buffer queue, thus in guarantee thread pool when comprising idle thread, can from buffer queue by task scheduling higher for execution priority in thread pool, to perform this task in time, decrease the stand-by period to the higher task of requirement of real-time.
Because the present embodiment is respectively at least one thread pool that each functional module creates, therefore, some idle threads may be had in setting-up time section, all can not be assigned to task, and these idle threads meeting occupying system resources, in a preferred embodiment of the invention, can when any one subject thread pond comprises idle thread, and this idle thread when not being assigned to required performing of task in setting-up time section, then destroy this idle thread, thus reduce the occupancy of system resource.
Cloud data center management platform comprises each functional module, virtual resources etc., in operational process, may the problem such as presence server fault, system failure, cause the interruption of cloud data center management platform, thus cause the interruption of performing in cloud data center management platform of task, and in the task of having no progeny cannot recover, lose the important information of user.
In a preferred embodiment of the invention, goal task can dispatched in any one subject thread pond in the process performed, the task main information that record object task is performed and task events information, and the task main information of record and task events information are stored in database;
Wherein, task main information comprises: at least one in the title of the unique identification of task, task names, affiliated functional module, executing state, task body, task creation time, job end time, task action result, implementation progress; Task events information comprises: task is performed the mark of each key point performed in process, the unique identification of task and task is performed to the explanation of each key point performed in process;
In cloud data center, management platform is interrupted, and after cloud data center management platform is restarted, according to task main information and the task events information of each task stored in database, the unclosed task of execution is loaded in its respective thread pond and continues to perform.
According to the program, even if cloud data center management platform is interrupted due to unknown cause, by the task main information of each task that stores in database and task events information unclosed for execution task can be loaded in its respective thread pond and continue to perform, ensure that the safety of user operation and the complete of information greatly.
For making the object, technical solutions and advantages of the present invention clearly, below in conjunction with drawings and the specific embodiments, the present invention is described in further detail.
Embodiments provide a kind of task management method based on cloud data center management platform, wherein, this cloud data center management platform can comprise: the large layer of operation layer, supporting layer and virtualization layer three, please refer to Fig. 2, wherein, the function responsibility of each level can comprise:
Virtualization layer, for encapsulating the API comprising the virtual manufacturer such as VMware, Xen, KVM, realizes the management to virtual machine, network, storage etc. in cloud data center management platform.Wherein, this virtual API is a kind of interface function, such as, creates the API of VMware virtual machine, if desired creating VMware virtual machine, can call this API and automatically creating VMware virtual machine for representing.
Supporting layer, can comprise virtual adaptation layer and platform adaptation layer, for carrying out differentiation encapsulation to the virtual type API of lower floor, provides unified interface to upper strata.
Operation layer, for calling the calculating of the interface management cloud data center of supporting layer, storage and Internet resources, carrying out various complex logic process and issued transaction, and providing external RESTAPI.
When operation layer gets goal task by RESTAPI, by calling the interface of supporting layer, to make supporting layer call API corresponding to this goal task, this goal task can be performed.
Please refer to Fig. 3, when operation layer dispatches the execution of this goal task, based on this cloud data center management platform, the task management method that the embodiment of the present invention provides can comprise the following steps:
Step 301: the configuration construction strategy of thread pool and the property parameters of thread pool.
In the present embodiment, the construction strategy of following thread pool can be configured: for each functional module in cloud data center management platform, thread pool that can be corresponding to the task creation for current functional module, also can to type belonging to the task for current functional module, such as, classification or accompanying method, create corresponding thread pool.Such as, be configured to ByClass, have such for mark in getting of task, this task scheduling can be performed in corresponding thread pool.If be configured to ByMethod, there is the method for mark in getting of task, this task scheduling can be performed in corresponding thread pool.
In the present embodiment, the property parameters of following thread pool can be configured: in the size of the maximum thread in main thread pond, the size in asynchronous thread pond, readjustment thread pool any one or multiple etc.Wherein, this main thread pond, during for not comprising the asynchronous thread pond to a certain task creation in systems in which, performs this task; Asynchronous thread pond, refers to the thread pool into some task or some type tasks create; Readjustment thread pool, when referring to that needs carry out readjustment process to the task of performing end, carries out these tasks adjusting back the thread pool processed.
In the present embodiment, the construction strategy of this thread pool and the property parameters of thread pool can be configured in Spring, to make directly to modify to configuration file in Spring according to service needed in subsequent process, without the need to reconfiguring the construction strategy of this thread pool and the property parameters of thread pool according to service needed, thus can system resource be saved, improve the efficiency of parameter configuration.
Step 302: according to the construction strategy of thread pool and the property parameters of thread pool, respectively for each functional module in cloud data center management platform, creates the thread pool of at least one.
In cloud data center, management platform comprises computing module, memory module and mixed-media network modules mixed-media, when creating thread pool, can for each functional module, create at least one thread pool, to enable, to should the task of functional module perform in for its thread pool created, to improve tasks carrying efficiency.
Step 303: obtain the goal task for objective function module from RESTAPI.
Such as, this goal task is the calculation task for computing module.
Step 304: judge whether to exist to should the thread pool of goal task, if exist, perform step 305; Otherwise, perform step 306;
Step 305: by asynchronous operation interface, goal task is dispatched to performing in the thread pool of goal task, perform step 309.
Step 306: judge whether further to exist to should the thread pool of type belonging to goal task, if exist, perform step 307; Otherwise, perform step 308;
Step 307: this goal task dispatched to performing in the thread pool of type belonging to goal task by asynchronous operation interface, perform step 309.
Step 308: dispatched by this goal task and perform in main thread pond, performs step 309.
In step 305, step 307 and step 308, when being dispatched by goal task to any one subject thread pond, this subject thread pond performs this goal task in the following way, please refer to Fig. 4, and which can comprise the steps:
Step 401: judge whether comprise idle thread in this subject thread pond, if comprise idle thread, utilizes this idle thread performance objective task; If do not comprise idle thread, continue to perform next step.
Step 402: judge that the Thread Count and first in this subject thread pond presets the relation that thread numerical value corePoolSize, second presets thread numerical value maximumPoolSize; Wherein, corePoolSize is less than maximumPoolSize; When Thread Count in this subject thread pond is less than corePoolSize, perform step 403; When Thread Count in this subject thread pond is not less than corePoolSize, and when being less than maximumPoolSize, perform step 404; When Thread Count in this subject thread pond equals maximumPoolSize, perform step 407.
Step 403: newly-built thread in this subject thread pond, and utilize this newly-built thread execution goal task, terminate.
Step 404: judge whether buffer queue comprises buffer further, if comprise, performs step 405; If do not comprise, perform step 406;
Step 405: the execution priority determining goal task, and according to the execution priority of the goal task determined, goal task is put into buffer queue, put into rear buffer queue to arrange according to execution priority order from small to large to direction of popping from stacked, to make in this subject thread pond when comprising idle thread, utilize idle thread according to the put in order performance objective task of goal task in buffer queue, terminate.
Step 406: newly-built thread in this subject thread pond, and utilize this newly-built thread execution goal task, terminate.
Step 407: refuse the process to goal task.
Wherein, the process of RejectedExecutionHandler refusal to goal task can be utilized.
In a preferred embodiment of the invention, some idle threads may be had in setting-up time section, all can not be assigned to task, and these idle threads meeting occupying system resources, therefore, can when any one subject thread pond comprises idle thread, and this idle thread when not being assigned to required performing of task in setting-up time section (keepAliveTime), then destroying this idle thread, thus reduce the occupancy of system resource.
Step 309: goal task is being dispatched in any one subject thread pond in the process performed, the task main information that record object task is performed and task events information, and the task main information of record and task events information are stored in database.
In the present embodiment, cloud data center management platform may further include: task persistence processor.This task persistence processor, may be used for the task main information and the task events information that record Processing tasks in main thread pond, asynchronous thread pond, readjustment thread pool, and the task main information of task and task events information is stored in database.
This task main information can comprise at least one in parameter as shown in table 1:
Table 1:
| Field | Explanation |
| Job_id | The unique identification of task |
| Job_name | Task names |
| Service_name | The title of affiliated functional module |
| Status | Executing state |
| Job | Task body |
| Create_time | The task creation time |
| End_time | Job end time |
| Op_result | Task action result |
| Op_process | Implementation progress |
Wherein, the executing state of task can be corresponding multiple, such as, hang up, run, failure, successfully etc.Job identifies task body, refers to the object of a binary mode.Create_time identifies the task creation time, if this tasks carrying terminates, then its task main information comprises End_time mark job end time; If this tasks carrying terminates, so also need in its task main information to comprise Op_result mark, for characterizing tasks carrying success or performing failed result, if perform failure, also can indicate the reason of failure.Op_process identifies the implementation progress of task.
Task events information can comprise parameter as shown in table 2:
Table 2:
| Field | Explanation |
| Id | Task is performed the mark of each key point performed in process |
| Job_id | The unique identification of task |
| Job_event | Task is performed to the explanation of each key point performed in process |
Wherein, in the process performing each task, may need to perform multiple key point, when performing each key point, the mark Id of this key point of execution can be recorded, and need the unique identification Job_id recording task corresponding to this key point, to make task main information associate with task events information, also need to record the explanation Job_event to this key point.
Step 310: management platform is interrupted in cloud data center, and after cloud data center management platform is restarted, according to task main information and the task events information of each task stored in database, the unclosed task of execution is loaded in its respective thread pond and continues to perform.
Because cloud data center management platform comprises each functional module, virtual resources etc., in operational process, may the problem such as presence server fault, system failure, cause the interruption of cloud data center management platform, thus cause the interruption of performing in cloud data center management platform of task, and in the task of having no progeny cannot recover, lose the important information of user.By the task main information of each task that stores in database and task events information, can determine which task not yet performs or not yet performs end, thus these tasks can be loaded in its respective thread pond and continue to perform, thus ensure that data security and complete.
In a preferred embodiment of the invention, can also be combined with the quartz of Spring, performing of task of fixing a point in timing scan database, execute the task to ensure the task that fixed point performs to add in thread pool, achieve the function that timing performs.
In a preferred embodiment of the invention, this cloud data center management platform can provide task management center, the operations such as user can delete task easily according to this task management center, cancel, recovery, in addition, user conveniently can check the details of certain tasks carrying, comprises implementation progress, performs failed reason, the key point etc. performed, convenient and swift.
Embodiments provide a kind of cloud data center management platform, please refer to Fig. 5, this cloud data center management platform can comprise:
Dispensing unit 501, for the construction strategy of thread pool that configures and the property parameters of thread pool;
Thread pool creating unit 502, for respectively for each functional module in cloud data center management platform, creates the thread pool of at least one, and wherein, at least one thread pool created for same functional module comprises main thread pond;
Acquiring unit 503, for obtaining the goal task for objective function module;
First judging unit 504, for judging whether to exist to should the thread pool of goal task, if existing, triggering scheduling unit 505 and being dispatched by goal task to performing in the thread pool of goal task; If do not exist, trigger the second judging unit and perform corresponding operating;
Second judging unit 506, for judging whether to exist to should the thread pool of type belonging to goal task, if existing, triggering scheduling unit 505 and being dispatched by this goal task to performing in the thread pool of type belonging to goal task; If do not exist, this goal task is dispatched and is performed in main thread pond by triggering scheduling unit 505.
Further, scheduling unit 505, for judging whether comprise idle thread in this subject thread pond, if comprise idle thread, utilizes this idle thread performance objective task; If do not comprise idle thread, continue to judge that the Thread Count and first in this subject thread pond presets the relation that thread numerical value, second presets thread numerical value; Wherein, the first default thread numerical value is less than the second default thread numerical value;
When Thread Count in this subject thread pond is less than the first default thread numerical value, newly-built thread in this subject thread pond, and utilize this newly-built thread execution goal task;
When Thread Count in this subject thread pond is not less than the first default thread numerical value, and when being less than the second default thread numerical value, judge whether buffer queue comprises buffer further, if comprise, goal task is put into buffer queue, to make in this subject thread pond, when comprising idle thread, to utilize idle thread performance objective task; If do not comprise, then newly-built thread in this subject thread pond, and utilize this newly-built thread execution goal task;
When Thread Count in this subject thread pond equals the second default thread numerical value, refuse the process to goal task.
Further, scheduling unit 505, for determining the execution priority of goal task, and according to the execution priority of the goal task determined, goal task is put into buffer queue, arranges according to execution priority order from small to large to direction of popping from stacked to make putting into rear buffer queue.
In a preferred embodiment of the invention, please refer to Fig. 6, this cloud data center management platform may further include: idle thread destroys unit 601, for when any one subject thread pond comprises idle thread, and this idle thread when not being assigned to required performing of task in setting-up time section, then destroy this idle thread.
Comprise further: record cell 602, for goal task being dispatched in any one subject thread pond in the process performed, the task main information that record object task is performed and task events information, and the task main information of record and task events information are stored in database;
Wherein, task main information comprises: at least one in the title of the unique identification of task, task names, affiliated functional module, executing state, task body, task creation time, job end time, task action result, implementation progress; Task events information comprises: task is performed the mark of each key point performed in process, the unique identification of task and task is performed to the explanation of each key point performed in process;
Comprise further: recovery unit 603, for interrupting in cloud data center management platform, and after cloud data center management platform is restarted, according to task main information and the task events information of each task stored in database, recover to perform unclosed task, to trigger scheduling unit, unclosed for execution task is loaded into continuation execution in its respective thread pond.
To sum up, the embodiment of the present invention at least can realize following beneficial effect:
1, in the embodiment of the present invention, by respectively for each functional module in cloud data center management platform, create at least one thread pool, to ensure when getting the goal task for objective function module, if at least one thread pool created comprise to should goal task thread pool or comprise should the thread pool of type belonging to goal task, then this goal task can be dispatched and perform in its respective thread pond, owing to being for each functional module creates at least one thread pool, this at least one thread pool created only performs the task of the corresponding function module, thus the stand-by period of tasks carrying can be reduced, improve Consumer's Experience.
2, in embodiments of the present invention, by when performing in task scheduling to thread pool, this thread pool performs this task on the backstage of system, and mutual between not influencing front stage and user, thus improve Consumer's Experience.
3, in the embodiment of the present invention, by determining the execution priority of goal task, and according to the execution priority of the goal task determined, goal task is put into buffer queue, arrange according to execution priority order from small to large to direction of popping from stacked to make putting into rear buffer queue, thus in guarantee thread pool when comprising idle thread, can from buffer queue by task scheduling higher for execution priority in thread pool, to perform this task in time, decrease the stand-by period to the higher task of requirement of real-time.
4, in the embodiment of the present invention, by when any one subject thread pond comprises idle thread, and when this idle thread is not assigned to required performing of task in setting-up time section, then destroys this idle thread, thus reduce the occupancy of system resource.
5, in the embodiment of the present invention, the task main information be performed by record object task and task events information, and the task main information of record and task events information are stored in database; In cloud data center, management platform is interrupted, and after cloud data center management platform is restarted, according to task main information and the task events information of each task stored in database, the unclosed task of execution is loaded in its respective thread pond and continues to perform.Even if cloud data center management platform is interrupted due to unknown cause, by the task main information of each task that stores in database and task events information unclosed for execution task can be loaded in its respective thread pond and continue to perform, ensure that the safety of user operation and the complete of information greatly.
The content such as information interaction, implementation between each unit in the said equipment, due to the inventive method embodiment based on same design, particular content can see in the inventive method embodiment describe, repeat no more herein.
It should be noted that, in this article, the relational terms of such as first and second and so on is only used for an entity or operation to separate with another entity or operational zone, and not necessarily requires or imply the relation that there is any this reality between these entities or operation or sequentially.And, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thus make to comprise the process of a series of key element, method, article or equipment and not only comprise those key elements, but also comprise other key elements clearly do not listed, or also comprise by the intrinsic key element of this process, method, article or equipment.When not more restrictions, the key element " being comprised a 〃 〃 〃 〃 〃 〃 " limited by statement, and be not precluded within process, method, article or the equipment comprising key element and also there is other same factor.
One of ordinary skill in the art will appreciate that: all or part of step realizing said method embodiment can have been come by the hardware that programmed instruction is relevant, aforesaid program can be stored in the storage medium of embodied on computer readable, this program, when performing, performs the step comprising said method embodiment; And aforesaid storage medium comprises: ROM, RAM, magnetic disc or CD etc. various can be program code stored medium in.
Finally it should be noted that: the foregoing is only preferred embodiment of the present invention, only for illustration of technical scheme of the present invention, be not intended to limit protection scope of the present invention.All any amendments done within the spirit and principles in the present invention, equivalent replacement, improvement etc., be all included in protection scope of the present invention.
Claims (10)
1. the task management method based on cloud data center management platform, it is characterized in that, be applied to the operation layer of described cloud data center management platform, the construction strategy of described operation layer according to pre-configured thread pool and the property parameters of thread pool, respectively for each functional module in cloud data center management platform, create the thread pool of at least one, wherein, at least one thread pool created for same functional module comprises main thread pond; Also comprise:
S1: obtain the goal task for objective function module;
S2: judge whether to exist to should the thread pool of goal task, if exist, dispatches to performing in the thread pool of goal task by goal task; If do not exist, perform S3;
S3: judge whether to exist to should the thread pool of type belonging to goal task further, if exist, dispatches to performing in the thread pool of type belonging to goal task by this goal task; If do not exist, perform S4;
S4: this goal task is dispatched and performs in main thread pond.
2. method according to claim 1, is characterized in that, described scheduling by goal task performs in any one subject thread pond, comprising:
Judge whether comprise idle thread in this subject thread pond, if comprise idle thread, utilize this idle thread to perform described goal task; If do not comprise idle thread, continue to perform next step;
Judge that the Thread Count and first in this subject thread pond presets the relation that thread numerical value, second presets thread numerical value; Wherein, the described first default thread numerical value is less than the described second default thread numerical value;
When Thread Count in this subject thread pond is less than the described first default thread numerical value, newly-built thread in this subject thread pond, and utilize goal task described in this newly-built thread execution;
When Thread Count in this subject thread pond is not less than the described first default thread numerical value, and when being less than the described second default thread numerical value, judge whether buffer queue comprises buffer further, if comprise, described goal task is put into described buffer queue, to make in this subject thread pond, when comprising idle thread, to utilize idle thread to perform described goal task; If do not comprise, then newly-built thread in this subject thread pond, and utilize goal task described in this newly-built thread execution;
When Thread Count in this subject thread pond equals the described second default thread numerical value, refuse the process to described goal task.
3. method according to claim 2, is characterized in that, described described goal task is put into described buffer queue, comprising:
Determine the execution priority of described goal task, and according to the execution priority of the described goal task determined, described goal task is put into described buffer queue, arranges according to execution priority order from small to large to direction of popping from stacked to make putting into rear described buffer queue.
4. method according to claim 2, is characterized in that, comprises further:
When any one subject thread pond comprises idle thread, and when this idle thread is not assigned to required performing of task in setting-up time section, then destroy this idle thread.
5., according to described method arbitrary in claim 1-4, it is characterized in that,
Comprise further: goal task is being dispatched in any one subject thread pond in the process performed, record task main information and task events information that described goal task is performed, and the task main information of record and task events information are stored in database;
Wherein, described task main information comprises: at least one in the title of the unique identification of task, task names, affiliated functional module, executing state, task body, task creation time, job end time, task action result, implementation progress; Described task events information comprises: task is performed the mark of each key point performed in process, the unique identification of task and task is performed to the explanation of each key point performed in process;
Comprise further: in cloud data center, management platform is interrupted, and after cloud data center management platform is restarted, according to task main information and the task events information of each task stored in database, the unclosed task of execution is loaded in its respective thread pond and continues to perform.
6. a Zhong Yun data center management platform, is characterized in that, comprising:
Dispensing unit, for the construction strategy of thread pool that configures and the property parameters of thread pool;
Thread pool creating unit, for respectively for each functional module in cloud data center management platform, creates the thread pool of at least one, and wherein, at least one thread pool created for same functional module comprises main thread pond;
Acquiring unit, for obtaining the goal task for objective function module;
First judging unit, for judging whether to exist to should the thread pool of goal task, if existing, triggering scheduling unit and being dispatched by goal task to performing in the thread pool of goal task; If do not exist, trigger the second judging unit and perform corresponding operating;
Second judging unit, for judging whether to exist to should the thread pool of type belonging to goal task, if existing, triggering scheduling unit and being dispatched by this goal task to performing in the thread pool of type belonging to goal task; If do not exist, this goal task is dispatched and is performed in main thread pond by triggering scheduling unit.
7. cloud data center according to claim 6 management platform, is characterized in that, described scheduling unit, for judging whether comprise idle thread in this subject thread pond, if comprise idle thread, utilizes this idle thread to perform described goal task; If do not comprise idle thread, continue to judge that the Thread Count and first in this subject thread pond presets the relation that thread numerical value, second presets thread numerical value; Wherein, the described first default thread numerical value is less than the described second default thread numerical value;
When Thread Count in this subject thread pond is less than the described first default thread numerical value, newly-built thread in this subject thread pond, and utilize goal task described in this newly-built thread execution;
When Thread Count in this subject thread pond is not less than the described first default thread numerical value, and when being less than the described second default thread numerical value, judge whether buffer queue comprises buffer further, if comprise, described goal task is put into described buffer queue, to make in this subject thread pond, when comprising idle thread, to utilize idle thread to perform described goal task; If do not comprise, then newly-built thread in this subject thread pond, and utilize goal task described in this newly-built thread execution;
When Thread Count in this subject thread pond equals the described second default thread numerical value, refuse the process to described goal task.
8. cloud data center according to claim 7 management platform, it is characterized in that, described scheduling unit, for determining the execution priority of described goal task, and according to the execution priority of the described goal task determined, described goal task is put into described buffer queue, arranges according to execution priority order from small to large to direction of popping from stacked to make putting into rear described buffer queue.
9. cloud data center according to claim 7 management platform, it is characterized in that, comprise further: idle thread destroys unit, for when any one subject thread pond comprises idle thread, and this idle thread when not being assigned to required performing of task in setting-up time section, then destroy this idle thread.
10., according to described cloud data center management platform arbitrary in claim 6-9, it is characterized in that,
Comprise further: record cell, for goal task being dispatched in any one subject thread pond in the process performed, record task main information and task events information that described goal task is performed, and the task main information of record and task events information are stored in database;
Wherein, described task main information comprises: at least one in the title of the unique identification of task, task names, affiliated functional module, executing state, task body, task creation time, job end time, task action result, implementation progress; Described task events information comprises: task is performed the mark of each key point performed in process, the unique identification of task and task is performed to the explanation of each key point performed in process;
Comprise further: recovery unit, for interrupting in cloud data center management platform, and after cloud data center management platform is restarted, according to task main information and the task events information of each task stored in database, recover to perform unclosed task, to trigger scheduling unit, unclosed for execution task is loaded into continuation execution in its respective thread pond.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510570007.1A CN105159768A (en) | 2015-09-09 | 2015-09-09 | Task management method and cloud data center management platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510570007.1A CN105159768A (en) | 2015-09-09 | 2015-09-09 | Task management method and cloud data center management platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105159768A true CN105159768A (en) | 2015-12-16 |
Family
ID=54800631
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510570007.1A Pending CN105159768A (en) | 2015-09-09 | 2015-09-09 | Task management method and cloud data center management platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105159768A (en) |
Cited By (38)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105760234A (en) * | 2016-03-17 | 2016-07-13 | 联动优势科技有限公司 | Thread pool management method and device |
| CN105912386A (en) * | 2016-05-03 | 2016-08-31 | 深圳市永兴元科技有限公司 | Thread management method and system |
| CN106020954A (en) * | 2016-05-13 | 2016-10-12 | 深圳市永兴元科技有限公司 | Thread management method and device |
| CN106095589A (en) * | 2016-06-30 | 2016-11-09 | 浪潮软件集团有限公司 | Partition allocation method, device and system |
| CN106095546A (en) * | 2016-06-01 | 2016-11-09 | 深圳市永兴元科技有限公司 | The task management method of cloud computing platform and device |
| CN106383749A (en) * | 2016-09-14 | 2017-02-08 | 郑州云海信息技术有限公司 | Thread management method and apparatus |
| CN106681840A (en) * | 2016-12-30 | 2017-05-17 | 郑州云海信息技术有限公司 | Tasking scheduling method and device for cloud operating system |
| CN106940658A (en) * | 2017-02-21 | 2017-07-11 | 腾讯科技（深圳）有限公司 | Task processing method and device based on thread pool |
| CN107172601A (en) * | 2017-04-20 | 2017-09-15 | 努比亚技术有限公司 | A kind of application message management platform and method |
| CN107783827A (en) * | 2016-08-31 | 2018-03-09 | 北京国双科技有限公司 | Asynchronous task processing method and processing device |
| CN107967549A (en) * | 2016-10-20 | 2018-04-27 | 南京途牛科技有限公司 | Multipaths Task Processing Unit and method |
| CN108009912A (en) * | 2017-11-30 | 2018-05-08 | 中国银行股份有限公司 | It is a kind of discharge he manage it ticket can use volume method for releasing and device |
| CN108345499A (en) * | 2018-02-01 | 2018-07-31 | 平安科技（深圳）有限公司 | Unified thread pool processing method, application server and computer readable storage medium |
| CN109358970A (en) * | 2018-10-18 | 2019-02-19 | 郑州云海信息技术有限公司 | A kind of method of cloud data center task management and task center |
| CN109542605A (en) * | 2018-11-27 | 2019-03-29 | 长沙智擎信息技术有限公司 | A kind of container group life cycle management method based on Kubernetes system architecture |
| CN109582472A (en) * | 2018-10-19 | 2019-04-05 | 华为技术有限公司 | A kind of micro services processing method and equipment |
| CN109766131A (en) * | 2017-11-06 | 2019-05-17 | 上海宝信软件股份有限公司 | The system and method for the intelligent automatic upgrading of software is realized based on multithreading |
| CN109947015A (en) * | 2019-03-15 | 2019-06-28 | 浙江中控技术股份有限公司 | The execution method and master controller of task |
| CN109976891A (en) * | 2019-03-28 | 2019-07-05 | 北京网聘咨询有限公司 | The server task processing method of task based access control thread configuration |
| CN109992414A (en) * | 2019-03-12 | 2019-07-09 | 平安普惠企业管理有限公司 | A thread pool-based task processing method and device |
| CN110046038A (en) * | 2019-03-12 | 2019-07-23 | 平安普惠企业管理有限公司 | A kind of task processing method and device based on thread pool |
| WO2019154130A1 (en) * | 2018-02-07 | 2019-08-15 | 阿里巴巴集团控股有限公司 | Task running method and apparatus, and electronic device |
| CN110287013A (en) * | 2019-06-26 | 2019-09-27 | 四川长虹电器股份有限公司 | The method for solving Internet of Things cloud service avalanche effect based on JAVA multithreading |
| CN110377412A (en) * | 2019-07-24 | 2019-10-25 | 湖南快乐阳光互动娱乐传媒有限公司 | Task scheduling method and system |
| CN110413390A (en) * | 2019-07-24 | 2019-11-05 | 深圳市盟天科技有限公司 | Thread task processing method, device, server and storage medium |
| CN110569112A (en) * | 2019-09-12 | 2019-12-13 | 华云超融合科技有限公司 | Log data writing method and object storage daemon device |
| CN110750339A (en) * | 2018-07-23 | 2020-02-04 | 杭州海康威视系统技术有限公司 | Thread scheduling method and device and electronic equipment |
| CN110991127A (en) * | 2019-10-17 | 2020-04-10 | 广东高云半导体科技股份有限公司 | Task execution method and device, computer equipment and storage medium |
| CN111049914A (en) * | 2019-12-18 | 2020-04-21 | 珠海格力电器股份有限公司 | Load balancing method and device and computer system |
| CN111782293A (en) * | 2020-06-28 | 2020-10-16 | 珠海豹趣科技有限公司 | Task processing method and device, electronic equipment and readable storage medium |
| CN111831410A (en) * | 2020-07-01 | 2020-10-27 | Oppo广东移动通信有限公司 | Task processing method and device, storage medium and electronic equipment |
| CN111831411A (en) * | 2020-07-01 | 2020-10-27 | Oppo广东移动通信有限公司 | Task processing method and device, storage medium and electronic equipment |
| CN113010290A (en) * | 2021-03-18 | 2021-06-22 | 山东英信计算机技术有限公司 | Task management method, device, equipment and storage medium |
| CN114463131A (en) * | 2022-02-09 | 2022-05-10 | 吉林亿联银行股份有限公司 | Transaction processing method and device, storage medium and electronic equipment |
| CN114546628A (en) * | 2022-04-22 | 2022-05-27 | 北京奥星贝斯科技有限公司 | Thread processing method, thread management method, thread processing device, thread management device and equipment |
| CN114642883A (en) * | 2022-03-31 | 2022-06-21 | 北京达佳互联信息技术有限公司 | Game management method and device and game server |
| CN114816759A (en) * | 2022-05-12 | 2022-07-29 | 未鲲(上海)科技服务有限公司 | Thread pool operation method and device, electronic equipment and storage medium |
| CN117707716A (en) * | 2023-05-26 | 2024-03-15 | 荣耀终端有限公司 | Thread scheduling method, electronic device and computer readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7565651B1 (en) * | 2000-05-25 | 2009-07-21 | Oracle International Corporation | Parallel task scheduling system for computers |
| CN103092712A (en) * | 2011-11-04 | 2013-05-08 | 阿里巴巴集团控股有限公司 | Method and device for recovering interrupt tasks |
| CN103197968A (en) * | 2013-03-18 | 2013-07-10 | 焦点科技股份有限公司 | Thread pool processing method and system capable of fusing synchronous and asynchronous features |
| CN103268247A (en) * | 2013-06-05 | 2013-08-28 | 中国电子科技集团公司第十五研究所 | Method and device for executing task and adjusting number of remaining threads in thread pool |
| CN104063279A (en) * | 2013-03-20 | 2014-09-24 | 腾讯科技（深圳）有限公司 | Task scheduling method and device and terminal |
-
2015
- 2015-09-09 CN CN201510570007.1A patent/CN105159768A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7565651B1 (en) * | 2000-05-25 | 2009-07-21 | Oracle International Corporation | Parallel task scheduling system for computers |
| CN103092712A (en) * | 2011-11-04 | 2013-05-08 | 阿里巴巴集团控股有限公司 | Method and device for recovering interrupt tasks |
| CN103197968A (en) * | 2013-03-18 | 2013-07-10 | 焦点科技股份有限公司 | Thread pool processing method and system capable of fusing synchronous and asynchronous features |
| CN104063279A (en) * | 2013-03-20 | 2014-09-24 | 腾讯科技（深圳）有限公司 | Task scheduling method and device and terminal |
| CN103268247A (en) * | 2013-06-05 | 2013-08-28 | 中国电子科技集团公司第十五研究所 | Method and device for executing task and adjusting number of remaining threads in thread pool |
Cited By (47)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105760234A (en) * | 2016-03-17 | 2016-07-13 | 联动优势科技有限公司 | Thread pool management method and device |
| CN105912386A (en) * | 2016-05-03 | 2016-08-31 | 深圳市永兴元科技有限公司 | Thread management method and system |
| CN106020954A (en) * | 2016-05-13 | 2016-10-12 | 深圳市永兴元科技有限公司 | Thread management method and device |
| CN106095546A (en) * | 2016-06-01 | 2016-11-09 | 深圳市永兴元科技有限公司 | The task management method of cloud computing platform and device |
| CN106095589B (en) * | 2016-06-30 | 2019-04-09 | 浪潮卓数大数据产业发展有限公司 | A kind of method, apparatus and system for distributing subregion |
| CN106095589A (en) * | 2016-06-30 | 2016-11-09 | 浪潮软件集团有限公司 | Partition allocation method, device and system |
| CN107783827A (en) * | 2016-08-31 | 2018-03-09 | 北京国双科技有限公司 | Asynchronous task processing method and processing device |
| CN106383749A (en) * | 2016-09-14 | 2017-02-08 | 郑州云海信息技术有限公司 | Thread management method and apparatus |
| CN107967549A (en) * | 2016-10-20 | 2018-04-27 | 南京途牛科技有限公司 | Multipaths Task Processing Unit and method |
| CN106681840A (en) * | 2016-12-30 | 2017-05-17 | 郑州云海信息技术有限公司 | Tasking scheduling method and device for cloud operating system |
| CN106940658A (en) * | 2017-02-21 | 2017-07-11 | 腾讯科技（深圳）有限公司 | Task processing method and device based on thread pool |
| CN106940658B (en) * | 2017-02-21 | 2022-09-09 | 腾讯科技（深圳）有限公司 | Task processing method and device based on thread pool |
| CN107172601A (en) * | 2017-04-20 | 2017-09-15 | 努比亚技术有限公司 | A kind of application message management platform and method |
| CN109766131A (en) * | 2017-11-06 | 2019-05-17 | 上海宝信软件股份有限公司 | The system and method for the intelligent automatic upgrading of software is realized based on multithreading |
| CN108009912A (en) * | 2017-11-30 | 2018-05-08 | 中国银行股份有限公司 | It is a kind of discharge he manage it ticket can use volume method for releasing and device |
| CN108345499A (en) * | 2018-02-01 | 2018-07-31 | 平安科技（深圳）有限公司 | Unified thread pool processing method, application server and computer readable storage medium |
| CN108345499B (en) * | 2018-02-01 | 2019-05-17 | 平安科技（深圳）有限公司 | Unified thread pool processing method, application server and computer readable storage medium |
| TWI696130B (en) * | 2018-02-07 | 2020-06-11 | 香港商阿里巴巴集團服務有限公司 | Task running method, device and electronic equipment |
| WO2019154130A1 (en) * | 2018-02-07 | 2019-08-15 | 阿里巴巴集团控股有限公司 | Task running method and apparatus, and electronic device |
| CN110750339B (en) * | 2018-07-23 | 2022-04-26 | 杭州海康威视系统技术有限公司 | Thread scheduling method and device and electronic equipment |
| CN110750339A (en) * | 2018-07-23 | 2020-02-04 | 杭州海康威视系统技术有限公司 | Thread scheduling method and device and electronic equipment |
| CN109358970A (en) * | 2018-10-18 | 2019-02-19 | 郑州云海信息技术有限公司 | A kind of method of cloud data center task management and task center |
| CN109582472A (en) * | 2018-10-19 | 2019-04-05 | 华为技术有限公司 | A kind of micro services processing method and equipment |
| CN109542605A (en) * | 2018-11-27 | 2019-03-29 | 长沙智擎信息技术有限公司 | A kind of container group life cycle management method based on Kubernetes system architecture |
| CN110046038A (en) * | 2019-03-12 | 2019-07-23 | 平安普惠企业管理有限公司 | A kind of task processing method and device based on thread pool |
| CN109992414A (en) * | 2019-03-12 | 2019-07-09 | 平安普惠企业管理有限公司 | A thread pool-based task processing method and device |
| CN109947015A (en) * | 2019-03-15 | 2019-06-28 | 浙江中控技术股份有限公司 | The execution method and master controller of task |
| CN109947015B (en) * | 2019-03-15 | 2020-08-28 | 浙江中控技术股份有限公司 | Task execution method and main controller |
| CN109976891A (en) * | 2019-03-28 | 2019-07-05 | 北京网聘咨询有限公司 | The server task processing method of task based access control thread configuration |
| CN109976891B (en) * | 2019-03-28 | 2020-11-03 | 北京网聘咨询有限公司 | Server task processing method based on task thread configuration |
| CN110287013A (en) * | 2019-06-26 | 2019-09-27 | 四川长虹电器股份有限公司 | The method for solving Internet of Things cloud service avalanche effect based on JAVA multithreading |
| CN110413390A (en) * | 2019-07-24 | 2019-11-05 | 深圳市盟天科技有限公司 | Thread task processing method, device, server and storage medium |
| CN110377412A (en) * | 2019-07-24 | 2019-10-25 | 湖南快乐阳光互动娱乐传媒有限公司 | Task scheduling method and system |
| CN110569112A (en) * | 2019-09-12 | 2019-12-13 | 华云超融合科技有限公司 | Log data writing method and object storage daemon device |
| CN110991127A (en) * | 2019-10-17 | 2020-04-10 | 广东高云半导体科技股份有限公司 | Task execution method and device, computer equipment and storage medium |
| CN111049914A (en) * | 2019-12-18 | 2020-04-21 | 珠海格力电器股份有限公司 | Load balancing method and device and computer system |
| CN111049914B (en) * | 2019-12-18 | 2021-02-09 | 珠海格力电器股份有限公司 | Load balancing method and device and computer system |
| CN111782293A (en) * | 2020-06-28 | 2020-10-16 | 珠海豹趣科技有限公司 | Task processing method and device, electronic equipment and readable storage medium |
| CN111831411A (en) * | 2020-07-01 | 2020-10-27 | Oppo广东移动通信有限公司 | Task processing method and device, storage medium and electronic equipment |
| CN111831410A (en) * | 2020-07-01 | 2020-10-27 | Oppo广东移动通信有限公司 | Task processing method and device, storage medium and electronic equipment |
| CN111831411B (en) * | 2020-07-01 | 2024-07-30 | Oppo广东移动通信有限公司 | Task processing method and device, storage medium and electronic equipment |
| CN113010290A (en) * | 2021-03-18 | 2021-06-22 | 山东英信计算机技术有限公司 | Task management method, device, equipment and storage medium |
| CN114463131A (en) * | 2022-02-09 | 2022-05-10 | 吉林亿联银行股份有限公司 | Transaction processing method and device, storage medium and electronic equipment |
| CN114642883A (en) * | 2022-03-31 | 2022-06-21 | 北京达佳互联信息技术有限公司 | Game management method and device and game server |
| CN114546628A (en) * | 2022-04-22 | 2022-05-27 | 北京奥星贝斯科技有限公司 | Thread processing method, thread management method, thread processing device, thread management device and equipment |
| CN114816759A (en) * | 2022-05-12 | 2022-07-29 | 未鲲(上海)科技服务有限公司 | Thread pool operation method and device, electronic equipment and storage medium |
| CN117707716A (en) * | 2023-05-26 | 2024-03-15 | 荣耀终端有限公司 | Thread scheduling method, electronic device and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105159768A (en) | Task management method and cloud data center management platform | |
| CN106802826B (en) | Service processing method and device based on thread pool | |
| KR102333341B1 (en) | Exception handling in microprocessor systems | |
| CN102508716B (en) | Task control device and task control method | |
| CN101727357B (en) | Method and apparatus for allocating resources in a compute farm | |
| EP2535810B1 (en) | System and method for performing distributed parallel processing tasks in a spot market | |
| EP2600246B1 (en) | Batch processing of business objects | |
| US20160139949A1 (en) | Virtual machine resource management system and method thereof | |
| US9471651B2 (en) | Adjustment of map reduce execution | |
| EP2357559A1 (en) | Performing a workflow having a set of dependancy-related predefined activities on a plurality of task servers | |
| US11526382B2 (en) | Cascading job scheduling in guests | |
| CN111338791A (en) | Scheduling method, device, device and storage medium for cluster queue resources | |
| EP3208709B1 (en) | Batch processing method and device for system invocation commands | |
| CN105573840A (en) | Event processing method and device in workflow operating period | |
| US10331488B2 (en) | Multilayered resource scheduling | |
| CN101093454A (en) | Method and device for executing SQL script file in distributed system | |
| CN101446906B (en) | Dispatching method for multi-batch processing tasks and system thereof | |
| KR101770191B1 (en) | Resource allocation and apparatus | |
| CN104750522A (en) | Dynamic execution method and system for tasks or processes | |
| US10678749B2 (en) | Method and device for dispatching replication tasks in network storage device | |
| CN113157411A (en) | Reliable configurable task system and device based on Celery | |
| EP2673704A1 (en) | Method and apparatus for moving a software object | |
| US9703601B2 (en) | Assigning levels of pools of resources to a super process having sub-processes | |
| CN112860401A (en) | Task scheduling method and device, electronic equipment and storage medium | |
| CN111160810A (en) | Workflow-based high-performance distributed spatial analysis task scheduling method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20151216 |