TW201512806A - System and method for handling waiting time of task - Google Patents

Abstract

The present invention provides a system for handling a waiting time of a task. The system is configured for: calculating a forecasting waiting time of a specific type of a task in a datacenter; sending the forecasting time to a client and displaying the forecasting time in the client; calculating a real waiting time after the specific type of the task has been handled; collecting statistics of the forecasting waiting time and the real waiting time in a period time, and calculating an adjusting value; adjusting the forecasting waiting time of the specific type of the task using the adjusting value.

Description

Task waiting time processing system and method

The present invention relates to a processing system and method, and more particularly to a task latency processing system and method.

At present, task processing (for example, patent application file transfer) is handled by the background service. After the user starts the task processing on the relevant page, the system will give a prompt (the case is being converted, please wait), however The user can't intuitively see how long the task processing has to wait, and the user can't predict the time that the task needs to wait. This will cause great trouble to the user. I don't know if I will continue to wait, or I can After completing other tasks and then processing the task, if you continue to wait, it may waste unnecessary waiting time. If you process it later, you don't know how long it will take to process it.

In view of the above, it is necessary to provide a task waiting time processing system and method, which can be used in advance to estimate the time that the task processing needs to wait, and dynamically update the waiting time according to the actual situation, so that after the user sees the time, It is convenient to decide whether to continue waiting or to handle other work according to the length of time.

A task waiting time processing system, the system running in a monitoring server, the system comprising: a computing module, configured to calculate an expected waiting time of a current data center for processing a specific type of task; a display module for the specific type The expected waiting time of the task is sent to the client and displayed on the client; the update module is used to update the expected waiting time of the specific type of task in time; the display module is also used to update the An estimated waiting time of the specific type of task is sent to the user end and displayed on the user end; the computing module is further configured to calculate an actual waiting for the specific type of task after the processing of the specific type of task is completed. Time; a correction module for counting the expected waiting time and the actual waiting time of the specific type of task for a certain period of time, and calculating a correction coefficient, and correcting the expected waiting time of the specific type of task according to the correction coefficient.

A task waiting time processing method is applied to a monitoring server, the method comprising: calculating an expected waiting time of a current data center for processing a specific type of task; and sending an expected waiting time of the specific type of task to the user end, and Displayed on the client; timely update the expected waiting time of the specific type of task; send the updated expected waiting time of the specific type of task to the client, and display it on the user; when the specific type After the task processing is completed, calculating the actual waiting time of the specific type of task; counting the expected waiting time and the actual waiting time of the specific type of task for a certain period of time, and calculating a correction coefficient, and correcting the specific type of task according to the correction coefficient Expected waiting time.

Compared with the prior art, the present invention provides a task waiting time processing system and method, which can pre-estimate the time that the task processing needs to wait, and dynamically update the waiting time according to the actual situation, so that after the user sees the time, It is convenient to decide whether to continue waiting or to handle other work according to the length of time.

10‧‧‧ Client

20‧‧‧Monitoring computer

30‧‧‧Database

40‧‧‧Network

50‧‧‧Data Center

500‧‧‧Server

200‧‧‧Task Waiting Time Processing System

210‧‧‧ Calculation Module

220‧‧‧ display module

230‧‧‧Update Module

240‧‧‧correction module

250‧‧‧Storage

260‧‧‧ processor

1 is an application environment diagram of a preferred embodiment of a task latency processing system of the present invention.

2 is a schematic structural view of a preferred embodiment of the monitoring computer of the present invention.

3 is a flow chart of a preferred embodiment of the task latency processing method of the present invention.

Referring to FIG. 1, an application environment diagram of a preferred embodiment of the task latency processing system 200 of the present invention is shown. The task waiting time processing system 200 is applied to the monitoring computer 20. The monitoring computer 20 is communicatively coupled to the data center (Data Center) 50 via the network 40.

The network 40 can be an internet, a regional network, or other communication network.

The data center 50 includes a plurality of servers 500 (four in the figure), and the server 500 is a blade server. The server 500 is used to process a task, which may be a file transfer (for example, converting a patent application file in a WORD format into a format of an officially specified patent application file), downloading a file, or uploading a file, etc. The task that the server automatically handles.

The monitoring computer 20 is configured to monitor the operation of the server 500 of the data center 50 to calculate the waiting time for processing each task in the data center 50 and present it to the client 10. The waiting time for each task includes an expected waiting time for each task and an actual waiting time for each task. The calculation of the waiting time for each task will be described in detail in Figures 2 and 3.

The monitoring computer 20 is also equipped with a Dynamic Host Configuration Protocol (DHCP) service, and the Internet Protocol (IP) address can be allocated to each server in the data center 50 through the DHCP service. The device 500 enables the monitoring computer 20 to communicate with the various servers 500 of the data center 50. The monitoring computer 20 can be a personal computer, a web server, or any other suitable computer. In addition, the monitoring computer 20 can also be placed inside the data center 50, that is, the monitoring computer 20 can also be a server in the data center 50. The user only needs to operate through the client terminal 10 to monitor the server 500 in the data center 50.

The monitoring computer 20 is coupled to the database 30 via a database connection. The database connection may be an Open Database Connectivity (ODBC) or a Java Database Connectivity (JDBC) connection. The database 30 is used to store data transmitted from the various servers 500 of the data center 50, including information such as expected waiting time and actual waiting time for each task.

It should be noted that the database 30 can be independent of the monitoring computer 20 or within the monitoring computer 20. The database 30 can be stored in a hard disk or flash storage disk of the monitoring computer 20. From the perspective of system security, the database 30 in this embodiment is independent of the monitoring computer 20.

The user terminal 10 provides a login interface of the data center 50. Through the login interface, the user can initiate processing of a certain task. For example, the user can upload a file to the data center 50 through the login interface, and then initiate a file transfer to the file. . The client 10 can be a personal computer, a laptop, a mobile phone, a tablet, and any other device that can be connected to the monitoring computer 20.

Referring to FIG. 2, it is a schematic structural view of a preferred embodiment of the monitoring computer 20 of the present invention. The monitoring computer 20 includes a task waiting time processing system 200. The task waiting time processing system 200 includes a computing module 210, a display module 220, an update module 230, and a correction module 240. The module referred to in the present invention is a computer program segment for performing a specific function, and is more suitable for describing the execution process of the software in the computer than the program. Therefore, the following description of the software is described in the module.

The computing module 210 is configured to calculate an expected waiting time for the current data center 50 to process a certain type of task. The expected waiting time for the certain type of task includes the estimated processing time of the type of task and the queuing time of the type of task (ie, the sum of the expected processing time of the type of task and the queuing time of the type of task). Specifically, the estimated processing time of the task of the type is calculated by testing a certain type of task in advance to obtain an average processing time of the task of the type, and the average processing time is the task of the type. Estimated processing time. When a task is started, the average processing time of the task is obtained according to the type of the task (such as a new application or a reply), which is the estimated processing time of the task. For example, the monitoring computer 20 sends an instruction to the data center 50 in advance, and requests the data center 50 to repeat a plurality of tests (for example, one hundred times) to process a certain type of task through a test, and record each time a task of the type is processed. Time, after which the computing module 210 calculates the average processing time of the task of the type and stores it in the database 30, when there is a task of this type, directly according to the type of the task (such as a new application or a reply) The average processing time of the task is obtained from the database 30, that is, the estimated processing time of the task is obtained.

The queuing time of the task of the type is calculated as follows: First, the total time for the data center 50 to process all tasks is calculated, and then divided by the number of servers 500 in the data center 50, thereby obtaining the queuing time of each task. The total time that the data center 50 processes all tasks is calculated as follows: the number of each task type included in the statistic center 50, and the estimated processing time for each type of task, the number of each task type multiplied by each category The expected processing time of the type of task is summed. For example, assume that data center 50 contains two types of tasks, counts the number of these two types of tasks, and sums the time of each type of task to arrive at the total time that data center 50 processes all tasks.

It should be noted that since the number of tasks processed in the data center 50 is dynamically changed (for example, the number of tasks is reduced by one after a certain task is processed), it is concluded that the queuing time of the tasks is dynamically changed. Further, the expected waiting time of the task is also dynamically changed.

The display module 220 is configured to send the expected waiting time of the task to the client 10 and display it on the client 10.

The update module 230 is configured to update the expected waiting time of the task of the type in time. Specifically, the update module 230 calculates the number of tasks in the data center 50 at a certain time (for example, five seconds) (that is, the number of tasks in the data center 50 is included), and calculates the latest type. The expected waiting time for the mission.

The display module 220 is further configured to send the updated waiting time of the updated task of the type to the client 10 and display it on the client 10.

The computing module 210 is configured to calculate an actual waiting time of the task of the type after the task processing of the type is completed. Specifically, the computing module 210 starts timing when the task of the type is started, and when the task processing of the type is completed, the actual waiting time for the processing of the task is recorded.

The correction module 240 is configured to count the estimated waiting time and the actual waiting time of the task of a certain period (for example, three days), and calculate a correction coefficient, and correct the expected waiting time of the task according to the correction coefficient. Specifically, after a period of accumulation, the correction module 240 statistically analyzes the estimated waiting time and the actual waiting time of the type of task, as shown in the following table:

Time Expected waiting time T1 Actual waiting time T2 Time difference T2-T1

As can be seen from the above table, because there are various uncertain factors, the actual waiting time and the expected waiting time are different. The time difference is calculated, and then the average value of the time difference is calculated. The above table can calculate the task of the type. The average time difference is 5 seconds (S), then 5 seconds is the correction factor S for this type of task, and the calculated time T1+S is taken as the predicted waiting time for display. In other words, the estimated waiting time for each task after correction is T1+5.

It should be noted that the correction module 240 needs to recalculate the correction coefficient every time (for example, one week), so that the subsequent calculation result is more accurate.

The correction module 240 also analyzes the cause and probability of the processing task sending error (the cause of the error is recorded in the log of the operating system, which can be read from the log, and the probability is based on the number of tasks in which the error occurred and the total number of tasks. Can be calculated).

As shown in FIG. 3, it is a flowchart of a preferred embodiment of the task waiting time processing method of the present invention.

In step S10, the calculation module 210 is configured to calculate an estimated waiting time for the current data center 50 to process a certain type of task. The expected waiting time for the certain type of task includes the estimated processing time of the type of task and the queuing time of the type of task (ie, the sum of the expected processing time of the type of task and the queuing time of the type of task). Specifically, the estimated processing time of the task of the type is calculated by testing a certain type of task in advance to obtain an average processing time of the task of the type, and the average processing time is the task of the type. Estimated processing time. When a task is started, the average processing time of the task is obtained according to the type of the task (such as a new application or a reply), which is the estimated processing time of the task. For example, the monitoring computer 20 sends an instruction to the data center 50 in advance, and requests the data center 50 to repeat a plurality of tests (for example, one hundred times) to process a certain type of task through a test, and record each time a task of the type is processed. Time, after which the computing module 210 calculates the average processing time of the task of the type and stores it in the database 30, when there is a task of this type, directly according to the type of the task (such as a new application or a reply) The average processing time of the task is obtained from the database 30, that is, the estimated processing time of the task is obtained.

The queuing time of the task of the type is calculated as follows: First, the total time for the data center 50 to process all tasks is calculated, and then divided by the number of servers 500 in the data center 50, thereby obtaining the queuing time of each task. The total time that the data center 50 processes all tasks is calculated as follows: the number of each task type included in the statistic center 50, and the estimated processing time for each type of task, the number of each task type multiplied by each category The expected processing time of the type of task is summed. For example, assume that data center 50 contains two types of tasks, counts the number of these two types of tasks, and sums the time of each type of task to arrive at the total time that data center 50 processes all tasks.

It should be noted that since the number of tasks processed in the data center 50 is dynamically changed (for example, the number of tasks is reduced by one after a certain task is processed), it is concluded that the queuing time of the tasks is dynamically changed. Further, the expected waiting time of the task is also dynamically changed.

In step S20, the display module 220 sends the expected waiting time of the task of the type to the client 10, and displays it on the client 10.

In step S30, the update module 230 timely updates the expected waiting time of the task of the type. Specifically, the update module 230 calculates the number of tasks in the data center 50 at a certain time (for example, five seconds) (that is, the number of tasks in the data center 50 is included), and calculates the latest type. The expected waiting time for the mission.

In step S40, the display module 220 sends the updated waiting time of the updated task of the type to the client 10, and displays it on the client 10.

In step S50, after the task processing of the type is completed, the calculation module 210 calculates the actual waiting time of the task of the type. Specifically, the computing module 210 starts timing when the task of the type is started, and when the task processing of the type is completed, the actual waiting time for the processing of the task is recorded.

In step S60, the correction module 240 counts the estimated waiting time and the actual waiting time of the task of the type for a certain period of time (for example, three days), and calculates a correction coefficient, and corrects the expected waiting time of the task according to the correction coefficient. Specifically, after a period of accumulation, the correction module 240 statistically analyzes the estimated waiting time and the actual waiting time of the type of task, as shown in the following table:

Time Expected waiting time T1 Actual waiting time T2 Time difference T2-T1

As can be seen from the above table, because there are various uncertain factors, the actual waiting time and the expected waiting time are different. The time difference is calculated, and then the average value of the time difference is calculated. The above table can calculate the task of the type. The average time difference is 5 seconds (S), then 5 seconds is the correction factor S for this type of task, and the calculated time T1+S is taken as the predicted waiting time for display. In other words, the estimated waiting time for each task after correction is T1+5.

It should be noted that the correction module 240 needs to recalculate the correction coefficient every time (for example, one week), so that the subsequent calculation result is more accurate.

The correction module 240 also analyzes the cause and probability of the processing task sending error (the cause of the error is recorded in the log of the operating system, which can be read from the log, and the probability is based on the number of tasks in which the error occurred and the total number of tasks. Can be calculated).

It should be noted that the above embodiments are only intended to illustrate the technical solutions of the present invention and are not intended to be limiting, and the present invention will be described in detail with reference to the preferred embodiments thereof The technical solutions are modified or equivalently substituted without departing from the spirit and scope of the technical solutions of the present invention.

no

10‧‧‧ Client

20‧‧‧Monitoring computer

30‧‧‧Database

40‧‧‧Network

50‧‧‧Data Center

500‧‧‧Server

200‧‧‧Task Waiting Time Processing System

Claims (10)

A task waiting time processing system, the system running in a monitoring server, the system comprising:
a calculation module for calculating an expected waiting time for a current data center to process a particular type of task;
a display module, configured to send an expected waiting time of the specific type of task to the user end, and display the same on the user end;
An update module for updating the expected waiting time of the particular type of task in time;
The display module is further configured to send the updated waiting time of the updated task of the specific type to the user end, and display the same on the user end;
The computing module is further configured to calculate an actual waiting time of the specific type of task after the processing of the specific type of the task is completed; and a correction module, configured to count the estimated waiting time of the specific type of task in a certain period of time And the actual waiting time, and calculate a correction factor to correct the expected waiting time of the particular type of task according to the correction coefficient. The task waiting time processing system of claim 1, wherein the estimated time of the particular type of task includes an estimated processing time of the particular type of task and a queuing time of the particular type of task. The task waiting time processing system of claim 2, wherein the estimated processing time of the specific type of task is calculated by testing the specific type of task to obtain an average processing of the specific type of task. Time, the average processing time for this particular type of task is the estimated processing time for that particular type of task. For example, in the task waiting time processing system described in claim 2, the queuing time of the specific type of task is calculated as follows: first calculate the total time of processing all tasks in the data center, and then divide by the servo in the data center. The number of devices, resulting in the queuing time for that particular type of task. For example, in the task waiting time processing system described in claim 4, the total time for processing all tasks in the data center is calculated as follows: the number of each task type included in the statistics center, and each type of each type is obtained. The estimated processing time of the task, the number of each task type multiplied by the expected processing time of each type of task and summed. A task waiting time processing method, which is applied to a monitoring server, the method comprising:
Calculate the estimated wait time for the current data center to handle a particular type of task;
Sending the expected waiting time of the specific type of task to the client, and displaying it on the client;
Update the expected waiting time for this particular type of task in a timely manner;
Sending the updated expected waiting time of the specific type of task to the client, and displaying it on the client;
After the processing of the specific type of task is completed, calculating the actual waiting time of the task of the specific type; and counting the expected waiting time and the actual waiting time of the specific type of task for a certain period of time, and calculating a correction coefficient, which is corrected according to the correction coefficient The estimated wait time for this particular type of task. The task waiting time processing method according to claim 6, wherein the estimated time of the specific type of task includes an estimated processing time of the specific type of task and a queuing time of the specific type of task. The task waiting time processing method according to claim 7, wherein the estimated processing time of the specific type of task is calculated by testing the specific type of task to obtain an average processing of the specific type of task. Time, the average processing time for this particular type of task is the estimated processing time for that particular type of task. For example, in the task waiting time processing method described in claim 7, the queuing time of the specific type of task is calculated as follows: first, calculating the total time of processing all tasks in the data center, and dividing by the servo in the data center The number of devices, resulting in the queuing time for that particular type of task. For the task waiting time processing method described in claim 9, the total time for processing all tasks in the data center is calculated as follows: the number of each task type included in the statistics center, and each type of The estimated processing time of the task, the number of each task type multiplied by the expected processing time of each type of task and summed.