CN111221636A

CN111221636A - Cross-service task progress measuring and displaying method and system

Info

Publication number: CN111221636A
Application number: CN201911410533.6A
Authority: CN
Inventors: 徐华; 于振坤
Original assignee: Beijing Bank Enterprise Integration Technology Development Co ltd
Current assignee: Beijing Jiehui Technology Co Ltd
Priority date: 2019-12-31
Filing date: 2019-12-31
Publication date: 2020-06-02

Abstract

The embodiment of the invention discloses a cross-service task progress measuring and displaying method and a cross-service task progress measuring and displaying system. The method comprises the following steps: the method comprises the steps that a progress bar with a unique number is created in a cache by a task initiating server, and the number is used as a parameter to be transmitted to a task executing server; the task execution server executes the tasks, and when the progress changes, the result of multiplying the progress increment by the ratio of the current task server to the total tasks is sent to a cache; and the terminal reads the progress data in the cache and updates the displayed progress value. By the method and the system, the execution progress of the serial tasks or the parallel tasks of the cross-service can be measured and displayed more timely and accurately.

Description

Cross-service task progress measuring and displaying method and system

Technical Field

The invention relates to the technical field of Internet. And more particularly, to a cross-service task progress metric and display method and system.

Background

Currently, a website server starts to adopt cluster deployment or micro-service deployment, and a plurality of servers execute a task together. In order to show the progress of the task, a commonly used showing tool is a "progress bar", that is, when the computer processes the task, the speed and the completion proportion of the processing task are displayed in a visual form in real time, and the size and the possible processing time of the remaining unfinished task are displayed in a rectangular bar shape.

However, the conventional progress bar can only display the progress of the task on the same server or the same micro-service, for example, publication No. CN104123214A discloses that the execution progress of the task and each sub-task thereof is measured based on runtime data generated by executing the task before the task and each sub-task therein, and the real-time progress of the execution of each sub-task of the task and the position to which the execution completion progress of each sub-task of the task is advanced are controlled and displayed. Specifically, at the server side, collecting runtime data generated by execution of each subtask in a kth task of the plurality of terminals, performing time series prediction based on historical runtime data and the runtime data generated by execution of each subtask in the kth task, updating the runtime data used for measuring the execution progress of the kth +1 th task and each subtask thereof, and sending the updated runtime data to the plurality of terminals. Further, this conventional algorithm is a serial execution method for tasks, and is not applicable to a parallel execution method.

Disclosure of Invention

The present invention aims to provide a solution to at least one of the problems of the prior art.

In order to achieve the purpose, the invention adopts the following technical scheme:

a cross-service task progress measurement and display method comprises the following steps:

s10, the task initiating server creates a progress bar with a unique number in the cache, and the number is used as a parameter to be transmitted to the task executing server;

s12, the task execution server executes the task, and when the progress changes, the result of multiplying the progress increment by the ratio of the current task server to the total task is sent to a cache; and

and S14, the terminal reads the progress data in the cache and updates the displayed progress value.

Alternatively,

the tasks are serial tasks and are executed in series by N task execution servers,

step S10 includes:

the initiating task server creates a progress bar in the cache and passes the unique number to the first executing task server in the serial task,

wherein N is a natural number greater than 1.

Optionally, step S12 includes:

the nth task execution server starts to execute the task, the increment and the unique number of the execution progress are sent to the cache, and the cache updates the latest progress of the progress bar with the unique number until the nth task execution server finishes executing the task;

the nth executive task server transmits the unique number to the (n +1) th executive task server, the (n +1) th executive task server starts executing the task, the increment of the execution progress and the unique number are sent to a cache, the cache updates the latest progress of the progress bar with the unique number until the (n +1) th executive task server finishes executing the task,

wherein N is more than or equal to 1 and less than N.

Alternatively,

the tasks are parallel tasks and are executed in parallel by M task execution servers,

step S10 includes:

the initiating task server creates a progress bar in the cache and transmits the unique number to M executing task servers in the parallel tasks,

wherein M is a natural number greater than 1.

Optionally, step S12 includes:

the nth executive task server starts executing the task, sends the increment of the execution progress and the unique number to the cache, and the cache updates the latest progress of the progress bar with the unique number until the nth executive task server finishes executing the task,

wherein n is more than or equal to 1 and less than or equal to M.

Optionally, step S14 includes

The terminal reads the progress data in the cache at a preset frequency, updates the displayed progress value,

wherein the predetermined frequency is higher than the frequency of executing the task server update progress increment.

Alternatively,

the terminal comprises a progress reading module and a display module,

wherein

The reading module reads the progress of the unique number at the preset frequency and sends the progress to a display module;

and the display module displays the progress.

Alternatively,

the display module displays the data in a percentage number form or a progress bar form with percentages.

Alternatively,

the initiating task server is one of the executing task servers.

In another aspect, the invention further provides a cross-service task progress measuring and displaying system, which comprises

Initiating task server, executing task server, cache and terminal, wherein

The method comprises the steps that a task initiating server creates a progress bar with a unique number in a cache, and the number is used as a parameter to be transmitted to a task executing server;

the task execution server executes the tasks, and when the progress changes, the result of multiplying the progress increment by the ratio of the current task server to the total tasks is sent to a cache; and

and the terminal reads the progress data in the cache and updates the displayed progress value.

The invention has the following beneficial effects:

by the method and the system, the execution progress of the serial tasks or the parallel tasks of the cross-service can be measured and displayed more timely and accurately.

Drawings

The following describes embodiments of the present invention in further detail with reference to the accompanying drawings;

fig. 1 shows a hardware architecture for implementing a method according to an embodiment of the invention.

Fig. 2 shows a flow diagram of a method according to an embodiment of the invention.

Detailed Description

In order to more clearly illustrate the invention, the invention is further described below with reference to preferred embodiments and the accompanying drawings. Similar parts in the figures are denoted by the same reference numerals. It is to be understood by persons skilled in the art that the following detailed description is illustrative and not restrictive, and is not to be taken as limiting the scope of the invention.

The method of the invention may be implemented in a hardware architecture 1 as shown in fig. 1, comprising a back-end server 10 performing tasks, shown for example as service a, service B and service N. In the present application, the expressions "service" and "server" may be substituted for each other. The hardware architecture 1 further comprises a cache 12 and a terminal 14. The terminal 14 may be a PC, a notebook, a PAD, or a mobile phone.

The method of the invention comprises the following steps:

and S10, creating a progress bar with a unique number in the cache by the task initiating server, and transmitting the number as a parameter to the task executing server.

And S12, the task execution server executes the task, and when the progress changes, the result of multiplying the progress increment by the ratio of the current task server to the total task is sent to the cache.

In a specific embodiment, the task is a serial task, that is, the server a executes the task first, the server a is handed to the server B to continue executing after the execution of the server a is completed, and the server B is handed to the server N to execute after the execution of the server B is completed. Wherein, the server A accounts for 30 percent, the server B accounts for 20 percent, and the server N accounts for 50 percent.

By the initiating task server A, a PROGRESS bar is created in the cache and returns the PROGRESS bar number PROGRESS _ 10000168. In this example, the server a is both an initiating task server and an executing task server that executes a part of the tasks. It will also be appreciated by those skilled in the art that the server initiating the task may not perform the task and be performed by other servers, the server initiating the task being responsible only for creating the progress bar in the cache.

The following example takes as an example that server a is both the initiating task server and the executing task server that executes the task.

Server a starts executing the task, sends the increment and number of PROGRESS of execution to the cache, which updates the latest PROGRESS of the PROGRESS bar numbered PROGRESS _10000168, as shown in table 1.

At time 10:00:01, the progress of the server A is 10%, at this time, the progress increment is 10%, the server A sends the result of multiplying the increment by 10% by the proportion of the server in the total task, namely, 3%, to the cache, and the cache updating progress is 3%.

At time 10:00:05, the progress of server a is 50%, at this time, the progress increment is 50% -10% + 40%, server a sends 12% of the result obtained by multiplying increment 40% by the percentage of 30% of the total tasks of the server to the cache, and the cache update progress is 3% + 12% + 15%.

And analogizing in sequence until the progress of the server A is 100% at the time 10:00:12, at this time, the progress increment is 100% -80% ═ 20%, the server A sends the result of multiplying the increment by 20% by 30% of the server in the total task to the cache, and the cache updating progress is 6% + 24% > -30%.

TABLE 1

The data (number) is transmitted to server B, which continues to execute the task and sends the increment and number of PROGRESS of execution to the cache, which updates the latest PROGRESS of the PROGRESS bar numbered PROGRESS _10000168, as shown in table 2.

At time 10:00:13, the progress of server B is 10%, at this time, the progress increment is 10%, server B sends 2% of the result obtained by multiplying the increment by 20% of the server in the total task to the cache, and the cache update progress is 2% + 30% (30% of the total progress that server a has completed) to 32%.

The rest of the time goes on and so on until server B finishes its duty 20%.

TABLE 2

The data is transmitted to server N, which continues to execute the task and sends the increment and number of PROGRESS of execution to the cache, which updates the latest PROGRESS of the PROGRESS bar numbered PROGRESS _10000168, as shown in table 3.

TABLE 3

The terminal reads the PROGRESS numbered PROGRESS _10000168 in the cache in real time and displays the PROGRESS on the user interface. Preferably, the reading frequency of the terminal is greater than the uploading frequency of the server, in this example, it is assumed that the reading frequency of the terminal is 2s, as shown in table 4. Because the reading frequency is greater than the uploading frequency, the updating progress of the display can be more timely and accurate.

Since the server A does not write progress increment update to the cache at the time 10:00:00, the cache progress read by the terminal at the time 10:00:00 is 0%, and 0% is displayed; at time 10:00:01, server a writes a progress increment of 3% to the cache, and at time 10:00:02, the terminal reads 3% of the progress of the cache at that time and displays 3%.

In one example, the terminal comprises a PROGRESS reading module and a display module, wherein the PROGRESS reading module reads the PROGRESS numbered PROGRESS _10000168 at a preset frequency and sends the PROGRESS to the display module. The display module displays the progress, and the display form may be a percentage number form or a progress bar form with percentages, which is not limited in the present invention.

TABLE 4

Terminal display	Terminal action	Time axis	Caching progress	Server side actions
					0％	Reading	10:00:00	0％
0％		10:00:01	3％	Writing in
					3％	Reading	10:00:02	3％
3％		10:00:03	3％
					3％	Reading	10:00:04	3％
3％		10:00:05	15％	Writing in
					15％	Reading	10:00:06	15％
15％		10:00:07	15％
					15％	Reading	10:00:08	15％
15％		10:00:09	24％	Writing in
					24％	Reading	10:00:10	24％
24％		10:00:11	24％
					30％	Reading	10:00:12	30％	Writing in
30％		10:00:13	30％
					30％	Reading	10:00:14	30％
30％		10:00:15	34％	Writing in
					34％	Reading	10:00:16	34％
34％		10:00:17	34％
					38％	Reading	10:00:18	38％	Writing in

In another embodiment, the task is a parallel task.

For example, the task needs to be processed by four servers in parallel, wherein server X is the server initiating the task, server a is 30% of the servers executing the task, server B is 20% of the servers executing the task, and server C is 50% of the servers executing the task. Wherein, those skilled in the art can understand that the server initiating the task may not participate in executing the task, and may also participate.

The following example takes X as an example of not participating in execution.

The server X which initiates the task creates a PROGRESS bar in the cache and returns the PROGRESS bar number PROGRESS _10000188, and the server X simultaneously transmits the PROGRESS bar to A, B, N three servers, and the three servers simultaneously start executing the task.

The data is transmitted to server a, which starts executing the task and sends the increment and number of PROGRESS of execution to the cache, which updates the latest PROGRESS of the PROGRESS bar numbered PROGRESS _ 10000188. As shown in table 5.

At time 10:00:01, server A is at 10% progress, at which time the progress increment is 10%, and server A sends the result 3% of the increment 10% multiplied by the server's 30% occupancy in the total task to the cache.

At time 10:00:09, server a is at 50% progress, with the progress increment being 50% -10% ═ 40%, server a sends the result 12% of the increment of 40% times the server's 30% of the total tasks to the cache.

And the analogy is repeated until the progress of the server A is 100% at the time 10:00:30, the progress increment is 20% when the progress increment is 100% -80%, and the server A sends the result of multiplying the increment by 20% by the ratio of the server to 30% in the total task to the cache, wherein the result is 6%.

TABLE 5

On the other hand, server B executes the task and sends the increment and number of execution PROGRESS to the cache, which updates the latest PROGRESS of the PROGRESS bar numbered PROGRESS _10000188, as shown in table 6.

At time 10:00:05, the progress of server B is 10%, at which time the progress increment is 10%, server B sends the result 2% of the increment 10% multiplied by the server's 20% of the total tasks to the cache.

At time 10:00:15, the progress of server B is 20%, at which time the progress increment is 20% -10% ═ 10%, server B sends the result 2% of the increment 10% multiplied by the server's percentage of 20% in the total task to the cache.

And so on until the progress of the server B is 100% at the time 10:00:26, at which time the progress increment is 60% for 100% -40%, the server a sends 12% of the result obtained by multiplying the increment of 60% by the server accounting for 20% of the total tasks to the cache.

TABLE 6

On the other hand, server N executes the task and sends the increment and number of execution PROGRESS to the cache, which updates the latest PROGRESS of the PROGRESS bar numbered PROGRESS _10000188, as shown in table 7.

At time 10:00:12, the progress of server N is 15%, at which time the progress increment is 15%, and server N sends the result of multiplying the increment of 15% by the server's percentage of 50% in the total task, 7.5%, to the cache.

At time 10:00:25, server N is at 40% progress, with the progress increment being 40% -15% ═ 25%, server N sends 12.5% to the cache of the increment 25% multiplied by the server's percentage of 50% of the total tasks.

And so on until the progress of the server N is 100% at time 10:00:35, at which time the progress increment is 15% for 100% -85%, and the server a sends the result of multiplying the increment of 15% by the server's percentage of 50% in the total task, 7.5%, to the cache.

TABLE 7

The terminal reads the PROGRESS numbered PROGRESS _10000188 in the cache in real time and displays the PROGRESS on the user interface. Preferably, the reading frequency of the terminal is greater than the uploading frequency of the server, in this example, it is assumed that the reading frequency of the terminal is 2s, as shown in table 8.

The terminal then reads the buffer progress at time 10:00:04, and since the buffer progress is not updated at this time, the display is still 3%.

At time 10:00:05, the server B writes a progress increment of 2% into the cache, at this time, the cache entry increment is updated to 5%, and at time 10:00:06, the terminal reads 5% of the progress of the cache at this time and displays 5%.

And so on thereafter.

TABLE 8

It is to be noted that, in the description of the present invention, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion.

It should be understood that the above-mentioned embodiments of the present invention are only examples for clearly illustrating the present invention, and are not intended to limit the embodiments of the present invention, and it will be obvious to those skilled in the art that other variations and modifications can be made on the basis of the above description, and all embodiments cannot be exhaustive, and all obvious variations and modifications belonging to the technical scheme of the present invention are within the protection scope of the present invention.

Claims

1. A cross-service task progress measurement and display method is characterized by comprising the following steps:

2. The method of claim 1,

step S10 includes:

wherein N is a natural number greater than 1.

3. The method according to claim 2, wherein step S12 includes:

wherein N is more than or equal to 1 and less than N.

4. The method of claim 1,

step S10 includes:

wherein M is a natural number greater than 1.

5. The method according to claim 4, wherein step S12 includes:

wherein n is more than or equal to 1 and less than or equal to M.

6. The method according to any one of claims 1 to 5, wherein step S14 includes

7. The method of claim 6,

the terminal comprises a progress reading module and a display module,

wherein

and the display module displays the progress.

8. The method of claim 7,

9. The method of claim 1,

the initiating task server is one of the executing task servers.

10. A cross-service task progress measurement and display system, comprising

Initiating task server, executing task server, cache and terminal, wherein