TW201324360A - Entrusted background execution encapsulated module - Google Patents

Abstract

The invention can automatically evoke the execution of module-encapsulated jobs in accordance with new jobs added by the user in an on-line system. The module employs the Semaphore theory to decide whether to execute or wait, if it is executable, the module employs the reflection mechanism to trigger the task entrusted by the user. When the task is completed, the system automatically notifies the task entrusting person via an Email and provides some related result information, and then continue with the execution of a next work after completion; if it is to wait, the job weight is automatically added in accordance with a weighting algorithm, thereby avoiding the phenomenon of a low-weight work never being executed . The invention provides an efficiency adjusting mechanism for achieving the adjustment of system operations and ensures the operation efficiency of entrusted works.

Description

Delivery background execution cladding module

The invention relates to a delivery background execution wrapping module, in particular to a control module for effectively controlling background work execution and application server system resource usage.

Delivery background execution method has always been a method commonly used by large systems. It is mainly used to process a large number of operations or requires a lot of time-consuming and resource-intensive work. On the one hand, users can wait for the result at the front end without wasting time. On the other hand, it can also avoid the burden of the system caused by such heavy work, so that the system can maintain sufficient resources for other functions to proceed. There are two types of traditional background execution modes, which are described as follows: waiting for scheduling: After the user delivers the task to the back end, the scheduling program is scheduled by the back end, and the scheduling execution time is mostly started when the system load is small, for example. In the early hours of the morning, the work thread execution is triggered after the time is up.

Execute immediately: After the user drops the backend, the system will trigger the thread to perform the work.

The delivery backend waits for scheduled execution. Although it can avoid affecting the operation of online system users, because the work is often delivered, it must wait until the scheduled time has elapsed before starting execution. It is more suitable for periodic work packages, but not suitable for Time-sensitive work package; the execution time of other work is often in the middle of the night. If there are any problems during the execution, it can only be processed after the system engineer is processed the next day, which will affect the system performance of the peak time of work.

The implementation mode is implemented immediately after the backend is delivered. The implementation mode is usually performed in multiple threads (Threads). After the thread finishes executing, the execution result is notified to the user that the task has been completed (for example, EMAIL). Suitable for time-sensitive tasks, and if there is an error during the execution period, the system administrator can usually handle it immediately. However, if the system triggers too many jobs at the same time, the system will increase the load, which will affect the system's performance, and even cause the system to stop service. Not only can the delivery work be completed, but other functions of the system will not be serviced.

Referring to Patent Publication No. 200707243, the asynchronous data query method and system, and the storage medium of the computer program for executing the method, the proposed patent only delivers the backend execution in an asynchronous manner, but the control of the backend thread and the system The load is not considered, and the main way to deliver the back-end is to adopt the immediate execution mode. However, the delivery of the back-end execution of the package module can improve the system's excessive burden caused by the system when the user uses it. Situation; and when the system is busy, the number of jobs executed by the delivery backend can be dynamically provisioned to ensure the stability of the system.

It can be seen that there are still many shortcomings in the above-mentioned conventional technology, which is not a good designer, but needs to be improved. In view of the shortcomings derived from the above-mentioned conventional technologies, the inventor of the present invention has improved and innovated, and after years of painstaking research, he finally succeeded in inventing a delivery background-encapsulating module.

The object of the present invention is to provide a more efficient and controllable delivery background execution module, which has the functions of providing time-sensitive tasks, taking into account system performance, dynamically adjusting the number of execution tasks, and dynamically adjusting work execution weights. In addition to solving the shortcomings of the traditional delivery back-end execution method, the system administrator can fully grasp the execution situation of the back-end task, improve the stability and output efficiency of the system, and reduce the cost of system management.

First, use the reflection and Threads of the high-level programming language to implement the delivery of the back-end wrapper module, and immediately start the work execution module after delivery to solve the traditional execution mode of the delivery as the delivery backend. To achieve the purpose of delivery must be time-sensitive.

The encapsulation module is combined with the database module and implemented as a Semaphore and a Weighting Queue, so that the encapsulation module can dynamically adjust the number of executables for the delivery of the backend, avoiding the traditional When too many back-end delivery tasks are executed at the same time, the system resources are insufficient, resulting in system interruption or slow situation, which seriously affects the stability of the system.

The invention additionally provides a back-end workload warning mechanism and statistical analysis data for providing back-end execution work, so as to provide a system administrator to optimize settings for the package module, and immediately present a problematic work list and error message. Reduce system errors and improve management time and management costs.

A delivery execution background module that achieves the above-described objects is a cladding module that is used to deliver a back-end execution program;

(1) Work Delivery Module: The delivery module stores the work delivered by the user in the database module, and the delivery module stores the work execution conditions and assigns the execution weight to the work according to the weighting rule;

(2) Work execution module: After the delivery module completes the delivery work, it will start a work execution module. The execution module first obtains the work with the highest weight in the current waiting work, and then according to the number of work executable by the system. Decide whether it is executable. If it cannot be executed, the system will start the dynamic adjustment weight module to recalculate the execution weight of the same category of work in the waiting process. This method can avoid the situation where the low weight work is difficult to be executed; if it is executable, it is executed. After completion, the result EMAIL will be notified to the front-end user. If the execution fails, EMAIL will notify the system administrator to continue the next job execution;

(3) Dynamic adjustment weight module: The work execution module delivers a dynamic adjustment weight module when the judgment delivery work cannot be executed immediately, and the module weights the work weights waiting for execution, and the weighting method is based on the weight algorithm. Define calculations;

Dynamic adjustment work module: The system administrator pre-defines the number of simultaneous executions of each delivery back-end work in the database module according to the type of each delivery work and the load caused by the system, and uses the application during the execution period. The server performance inspection tool obtains the load of the system, and obtains the execution status of each delivery backend through the management interface. The system administrator comprehensively increases and decreases the number of work performed by the backend to improve the output of the system and Maintain system stability.

Please refer to FIG. 1 , which is a functional module diagram of the execution module of the present invention, including: a plurality of terminal servers 1 , which can be simultaneously connected to the application server 2 to perform a delivery task. A database server (DB Server) 3 is used to store execution parameters, work execution situations, and related execution records for delivery background execution. An application server (AP Server) 2 stores the parameters for delivering the back-end execution work in the database server (DB Server) 3 according to the service request proposed by the terminal server 1, and then performs various tasks according to the work execution conditions. The program includes the following modules:

The work delivery module 201 has a browser interface for processing user job delivery operations, and each job has its corresponding business logic component 205. The interface provides input of each work requirement parameter according to the user's usage authority, and after delivery, after delivery Verify the rationality of all parameters before execution, and then pass the user to the execution of the work to deliver the backend execution; deliver the module and provide the query interface for the work execution process and results, so that the user can master the work execution status;

The work execution module 202 has a work evoke execution function and is responsible for processing the execution of the delivery backend execution work. The work execution module 202 is started after the work delivery module 201. After the startup, the module will obtain the most weighted work in various types of work in the work waiting for execution, and then determine the number of work executables by controlling the Semaphore module 301. Whether the system has set an upper limit to determine whether the delivery work is allowed to be executed. If it is executable, the module uses the Reflection technology to trigger the commercial logic component 205 of the work, and starts execution. If any error occurs during the process, the module borrows The exception analysis mechanism records the error message into the database module, and notifies the system administrator of the error by EMAIL, so as to facilitate the subsequent error processing; if the normal execution ends, the execution module will notify the record according to the execution parameter. The front-end user is executed;

The dynamic adjustment weight module 203 has a recalculation work weight function and is responsible for recalculating the weight of the waiting work. After the work execution module 202 determines that the work still has to wait, the dynamic adjustment weight module 203 will recalculate the weight of the waiting work according to the weight algorithm, and the weight algorithm formula is Wa= The parameters are as follows:

● Wa: weighted weight value

● Wb: weighted pre-weight value

● F: the weighting factor defined by the system administrator in advance

● DWTO: Descending waiting-time order, which represents the descending ordering of similar work waiting times.

The length of the waiting time and the weighting weighting factor all affect the weight of the recalculated. The weighting weighting factor can be dynamically adjusted. This module can make the work with low weight but longer waiting time increase the weight and avoid the Starvation phenomenon.

The dynamic adjustment working module 204 has an adjustment module capable of executing the number of work, and provides the system administrator to flexibly adjust the number of executable work according to the current situation of the system. The module allows the system administrator to avoid the system peak period. Performing the work of delivering the background execution can also maximize system output under the tolerance of system resources;

The work business logic component 205, having the code of the work business logic, is implemented by the programmer. The component is developed using the shared interface function provided by the wrap module, and the wrap module can be triggered during the execution phase. Component, the business logic program responsible for the completion of the component, A, B, C in the figure represent different working business logic components;

The Semaphore module 301 is provided with a storage module for storing the Semaphore state, which is used for controlling the number of Semaphores that can be used for each job, and observing the current state of use of the Semaphore, and stably adjusting the working module 204 to stabilize the system. Output efficiency; a system that provides controllable delivery background execution if there are many functions that require significant system resources and non-immediacy, such as a large number of queries, documentation functions, or methods that are performed using traditional delivery backends. The module improves the shortcomings of traditional delivery background execution methods, adding timeliness and performance control features. The module includes two execution phases: a delivery phase, an execution phase, and a dynamic adjustment work module 204, as follows:

Delivery phase: The delivery phase generally refers to the front-end user inputting the work execution parameters to the terminal server, and then sending the entire program to the database for storage, which is called the delivery phase. The wrapper module provides a standardized program interface and library, allowing the programmer to store the execution parameters required for the work in the database module. The rationality of the work execution parameters needs to be determined by the programmer. When the work delivery module 201 is stored in the database, the execution weight of the work is given according to the scope of the work parameters and the authority of the executor, that is, the work delivery phase is completed, and the subsequent wrapping module enters the work execution phase;

Execution phase: The execution phase generally means that after each work delivery phase is completed, the wrap module will automatically start the work execution phase program. Figure 2 is a flow chart of the executable work in the execution phase, as detailed below:

1. According to the work category, obtain the corresponding Semaphore from the Semaphore Pool in the database module, and obtain the work with the greatest weight in the work pool to prepare for execution.

2. From the database, read the execution parameters of the job.

3. The business logic component 205 that triggers the work is triggered by the Java Reflection mechanism, and the execution state is recorded in the database module.

4. After the execution is completed, start EMAIL to notify the user to execute the result.

5. Return to step 1 until there is no waiting work to perform.

In the execution stage, if there is no corresponding Semaphore available for such work, the dynamic adjustment weight module 203 will recalculate the work weights waiting to be executed according to the weight algorithm, moderately increase its weight, and can avoid low weight. Work is harder to implement.

Dynamic adjustment work module 204: The system administrator dynamically adjusts the number of Semaphores by using the work execution status recorded in the database module and the performance checker provided by the application server to obtain the maximum output and stability of the system. .

The present invention provides a wrapper module for delivering backend execution, which is implemented by using Threads, reflection characteristics of a programming language, transaction characteristics (Transaction), and Weighting Queue. The module, in addition to the Semaphore principle to control the delivery of the back-end work while executing the number, compared with the aforementioned citations and other conventional techniques, has the following advantages:

● Streamlined application development time: Through the Reflection feature, the programmer only needs to focus on the business logic of the development task, without having to deal with the rest of the delivery backend and the control execution of the work execution stage, greatly reducing the program repetitive code generation rate. Improve the efficiency of the programmer.

● System performance control and timeliness: The system administrator can dynamically adjust the number of Semaphores for each back-end work to increase the output of the system; or adjust the work weights individually for the work characteristics, so that the work can be given the highest priority. Execution, meeting the requirements of timeliness.

● Provides a productivity analysis and debugging interface for delivering back-end work: With each execution record of the back-end job, system administrators can easily get a record of the time or error of each job execution.

● Dynamic adjustment mechanism of work weight: When the system is busy, the system automatically increases the weight of waiting for execution, ensuring that the system can be executed immediately when the system is idle, and avoiding the problem that low-weight work is difficult to be executed.

The above detailed description is only to be construed as illustrative of the preferred embodiments of the invention. Changes should be included in the scope of the patent in this case.

In summary, this case is not only innovative in terms of technical application ideas, but also enhances the above-mentioned multiple functions by the well-known methods. It should fully comply with the statutory invention patent requirements of novelty and progressiveness, and apply for it according to law. The bureau approved the application for the invention patent, in order to invent the invention, to the sense of virtue.

1. . . Terminal server

2. . . Application server

3. . . Database server

201. . . Work delivery module

202. . . Work execution module

203. . . Dynamic adjustment weight module

204. . . Dynamic adjustment work module

205. . . Work business logic

301. . . Control Semaphore Module

Figure 1 is a functional module diagram of the delivery background module of the present invention

Figure 2 is a system flow diagram of the execution phase of the present invention executing the cladding module in the present invention

1. . . Terminal server

2. . . Application server

3. . . Database server

201. . . Work delivery module

202. . . Work execution module

203. . . Dynamic adjustment weight module

204. . . Dynamic adjustment work module

205. . . Work business logic

301. . . Control Semaphore Module

Claims (8)

A delivery background execution wrapping module includes: a database server for storing work execution parameters delivered by the work execution module, control code module setting data, delivery work execution history and error message records; The device is used to centralize and provide an execution platform for each delivery end to perform work, and access the work data to the database server through the network; and a terminal server for connecting to the application server To perform delivery tasks. The delivery background execution wrapping module as described in claim 1 wherein the application server further comprises a work delivery module configured to process the execution parameters of the terminal server delivery execution work. Sexual verification, and the execution weight given to the execution work according to the weighting rule, and used to start the work execution module. The delivery background execution wrapping module of claim 1, wherein the application server further comprises a work execution module for obtaining execution parameters and determining whether the execution weight of the execution work is Execute, then start the work business logic component. The delivery background execution wrapping module of claim 1, wherein the application server further comprises a working business logic component, the working business logic component comprising a common interface function, the common interface function system To initiate the interface of the working business logic component. The delivery background execution wrapping module as described in claim 1, wherein the application server further comprises a dynamic adjustment weight module, when the work execution module cannot perform the work of determining delivery immediately, The dynamic adjustment weight module weights the work weights awaiting execution according to the weighting algorithm. The delivery background execution encapsulation module as described in claim 1 , wherein the application server further comprises a dynamic adjustment work module, which provides a system administrator to dynamically adjust the number of executions of various types of work, and To dynamically adjust the number module. The delivery background execution wrapping module as described in claim 1 wherein the application server further comprises a control number module, which provides various Semaphore records and related use cases for delivering backend work. To collect and analyze relevant information. For example, the delivery background execution wrapping module described in claim 5, wherein the weighting algorithm is based on a weighting factor, a waiting time sorting, and an original working weight as a basis for weighting weight calculation, and then calculating a new mathematical model. Weight value.