Report task scheduling method and device, electronic equipment and storage medium
By analyzing the production and access logs of the reporting system, the priority and start time of scheduling tasks are dynamically adjusted, which solves the problem of limited computing resources in the existing reporting system and realizes intelligent task scheduling and improved user satisfaction.
Patent Information
- Application Number
- CN202110901967.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-08-06
- Publication Date
- 2025-11-25
- Estimated Expiration
- 2041-08-06
AI Technical Summary
The existing reporting system, with limited computing resources, is unable to meet the access needs of users across various business lines. Furthermore, the existing scheduling strategy suffers from task backlog or idle resources, requiring manual optimization and resulting in untimely responses.
By acquiring production logs and access logs, analyzing relevant characteristic data, dynamically adjusting the priority and start time of scheduled tasks, and optimizing task configuration using intelligent scheduling strategies.
The system enables intelligent task scheduling for the reporting system, promptly meeting user needs, improving system service satisfaction, reducing manual intervention, and increasing operational efficiency.
Smart Images

Figure CN115705237B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of data processing technology, specifically to a report task scheduling method, apparatus, electronic device, and storage medium. Background Technology
[0002] Report generation is a crucial component of any reporting system, and its task scheduling strategy is key to the satisfaction of users in accessing report queries. For example, a provincial / municipal reporting system might handle multiple reports for various departments within the province / city. Given limited computing resources and a large number of reports, ensuring and improving user satisfaction with report query services across different departments presents challenges. New reports added monthly to the required version can impact the efficiency of generating existing reports, and users across different departments have varying needs and access times. Therefore, a reasonable report task scheduling strategy is necessary to ensure the access needs of all departments are met and to avoid disrupting their operations. Current methods rely on manually preset fixed time points for scheduling, which can lead to task backlogs or idle computing resources. Furthermore, the scheduling parameters can only be adjusted based on user feedback. This approach fails to guarantee that all users' access needs are met and requires reactive manual adjustment of scheduling parameters, resulting in slow response times. Summary of the Invention
[0003] Based on the problems existing in the prior art, this invention proposes a report task scheduling method, device, electronic device, and storage medium.
[0004] In a first aspect, embodiments of the present invention provide a report task scheduling method, including:
[0005] Retrieve the production logs and access logs for the report;
[0006] Based on the production logs and access logs of the report, relevant feature data of the report are obtained;
[0007] Based on the relevant feature data of the report, the adjustment priority of the scheduling task of the report is obtained;
[0008] Based on the adjustment priority of the scheduling task according to the report and the access time of the report, the start time of the scheduling task is adjusted according to the corresponding adjustment strategy.
[0009] In some examples, the relevant feature data of the report includes at least the report's production cost feature data and the report's access requirement feature data.
[0010] In some examples, the production cost characteristic data includes the report's related computational resource weights, time consumption weights, and completion time points, and the access demand characteristic data includes the report's related access frequency weights and access time points;
[0011] The step of obtaining the adjustment priority of the scheduling task for the report based on the relevant feature data of the report includes:
[0012] Based on the computational resource weight, time consumption weight, and completion time, the production cost factor is obtained;
[0013] Based on the access frequency weight and access time point, the access demand factor is obtained;
[0014] Based on the production cost factor and the access demand factor, the adjustment priority of the scheduling task for the report is obtained.
[0015] In some examples, the access demand factor = access frequency weight / overall access frequency weight; the production cost = calculation resource weight * 50% + time consumption weight / overall time consumption weight * 50%.
[0016] In some examples, the adjustment priority of the report-based scheduling task and the report access time are adjusted according to a corresponding adjustment strategy to adjust the start time of the scheduling task, including:
[0017] If the access time of the report is earlier than the completion time, the start time of the report's scheduling task will be adjusted positively; otherwise, the start time of the report's scheduling task will be adjusted negatively.
[0018] In some examples, the priority of the scheduling tasks for the reports includes Level 1 key support reports, Level 2 important support reports, Level 3 minor support reports, and Level 4 general support reports.
[0019] In some examples, if the report access time is earlier than the completion time, the start time of the report's scheduling task is adjusted positively; otherwise, the start time of the report's scheduling task is adjusted negatively, including:
[0020] For Level 1 key protection reports, adjustments are made using an adjustment strategy that maximizes the positive step size or minimizes the negative step size.
[0021] For critical support reports at Level 2, adjust the scheduling strategy by shortening the positive step size or increasing the negative step size.
[0022] For Level 3 secondary support reports, continue to adjust the scheduling strategy by shortening the positive step size or increasing the negative step size;
[0023] For Level 4 general protection reports, adjustments are made using the smallest positive step size or the largest negative step size adjustment strategy.
[0024] Secondly, embodiments of the present invention provide a report task scheduling device, comprising:
[0025] The acquisition module is used to acquire the production logs and access logs of the reports;
[0026] The feature acquisition module is used to obtain relevant feature data of the report based on the production log and access log of the report;
[0027] The priority determination module is used to determine the adjustment priority of the scheduling task of the report based on the relevant feature data of the report;
[0028] The task scheduling module is used to adjust the priority of scheduled tasks based on reports and the access time of the reports, and adjust the start time of the scheduled tasks according to the corresponding adjustment strategy.
[0029] Thirdly, embodiments of the present invention also provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the report task scheduling method as described in the first aspect.
[0030] Fourthly, embodiments of the present invention also provide a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the report task scheduling method as described in the first aspect.
[0031] As can be seen from the above technical solutions, the report task scheduling method, device, electronic device and storage medium provided in the embodiments of the present invention can promptly detect situations where the report system fails to satisfy users, and intelligently adapt the report task scheduling configuration to user behavior, thereby improving system service satisfaction. Attached Figure Description
[0032] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.
[0033] Figure 1 This is a flowchart of a report task scheduling method provided in an embodiment of the present invention;
[0034] Figure 2 This is a schematic diagram of task hierarchy in a report task scheduling method provided in an embodiment of the present invention;
[0035] Figure 3This is a structural block diagram of a report task scheduling device provided in an embodiment of the present invention;
[0036] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation
[0037] The specific embodiments of the present invention will be further described below with reference to the accompanying drawings. The following examples are only used to more clearly illustrate the technical solutions of the present invention and should not be construed as limiting the scope of protection of the present invention.
[0038] The following describes, with reference to the accompanying drawings, a report task scheduling method, apparatus, electronic device, and storage medium according to embodiments of the present invention.
[0039] Figure 1 A flowchart of a report task scheduling method according to an embodiment of the present invention is shown. Figure 1 As shown, an embodiment of the present invention provides a report task scheduling method, which includes the following:
[0040] S101: Obtain the production logs and access logs of the report.
[0041] The report production process is as follows: data collection to light aggregation, light aggregation to scheduled aggregation, scheduled aggregation to report display. Each step's completion is logged in a task completion log table for use by subsequent steps. Data collection is performed using ETL tools from NGBOSS production database nodes in various cities or external system file interfaces. Then, light aggregation using Hadoop MapReduce and high-level aggregation using DB2 SQL are used, ultimately providing the report for querying and downloading on the reporting system's front end.
[0042] The process of report production, from data collection and light aggregation to high-level aggregation, is inherently complex. Different reports have different prerequisite tasks, and different cities or business lines have different access requirements for reports, resulting in varying production costs. Therefore, it is necessary to establish an intelligent task scheduling and management model to optimize the parameters of report task scheduling in a reasonable and dynamic manner.
[0043] The data preparation stage involves acquiring production and access logs for reports. Specifically, production logs (such as those from report collection and statistics) and user logs (such as those from report access) describe, to some extent, the production cost and user needs of each report. If a value model for each report can be found by mining this data, this model can guide the orchestration of report task scheduling, achieving intelligent report task scheduling and management.
[0044] S102: Based on the production logs and access logs of the report, obtain the relevant feature data of the report.
[0045] As can be seen from the above features, the relevant feature data of the report includes, but is not limited to, the report's production cost feature data and the report's access requirement feature data. In this example, the production cost feature data includes, but is not limited to, the report's relevant computing resource weights, time consumption weights, and completion time points, while the access requirement feature data includes, but is not limited to, the report's relevant access frequency weights and access time points.
[0046] Specifically, the raw data such as the production logs and user logs (i.e., access logs) of the reporting system are cleaned and processed to obtain a series of standardized feature data (i.e., report-related feature data), as shown in Tables 1 to 3:
[0047] Table 1
[0048]
[0049] Table 1 shows the production cost characteristics data.
[0050] Table 2
[0051]
[0052] Table 2 shows the access demand characteristic data.
[0053] Table 3
[0054]
[0055] Table 3 shows the initial level of task scheduling configuration for the report.
[0056] S103: Based on the relevant feature data of the report, obtain the adjustment priority of the report's scheduling task.
[0057] In a specific example, based on the relevant feature data of the report, the adjustment priority of the report's scheduling task is obtained, including: obtaining a production cost factor based on the computational resource weight, time consumption weight, and completion time; obtaining an access demand factor based on the access frequency weight and access time; and obtaining the adjustment priority of the report's scheduling task based on the production cost factor and the access demand factor. In this example, the access demand factor = access frequency weight / overall access frequency weight; the production cost factor = computational resource weight * 50% + time consumption weight / overall time consumption weight * 50%.
[0058] In the example above, the priority adjustment of report scheduling tasks includes Level 1 key support reports, Level 2 important support reports, Level 3 secondary support reports, and Level 4 general support reports. That is, by dividing the data into two-dimensional coordinate axes of "Access Request (Need)" and "Production Cost (Cost)," as follows... Figure 2The priority of report task scheduling for each city is divided into four levels, from high to low. Table 4 shows the report task classification rules.
[0059] Table 4
[0060] Report hierarchy Access demand factor Production cost factor 1. Prioritize reporting High (0.5, 1) Low (0, 0.5) 2. Important Guarantee Reports High (0.5, 1) High (0.5, 1) 3. Secondary Guarantee Report Low (0, 0.5) Low (0, 0.5) 4. General Guarantee Report Low (0, 0.5) High (0.5, 1)
[0061] In other words, the priority ranking calculation formula for report tasks falling within the same level region is: adjustment is calculated as follows: county-level ranking factor - access demand factor * 80% + production cost factor * 20%.
[0062] S104: Based on the adjustment priority of the scheduling task and the access time of the report, adjust the start time of the scheduling task according to the corresponding adjustment strategy.
[0063] Specifically, based on the adjustment priority of the report's scheduling task and the report's access time, the start time of the scheduling task is adjusted according to the corresponding adjustment strategy, including: if the report's access time is earlier than its completion time, the start time of the report's scheduling task is adjusted positively; otherwise, the start time of the report's scheduling task is adjusted negatively.
[0064] Taking the adjustment priorities from level 1 to level 4 as an example, the specific start times for their adjustment scheduling tasks include: for level 1 key support reports, the adjustment strategy is to adjust with the largest positive step size or the smallest negative step size; for level 2 important support reports, the adjustment strategy is to adjust with the shortened positive step size or the increased negative step size; for level 3 secondary support reports, the adjustment strategy continues to adjust with the shortened positive step size or the increased negative step size; for level 4 general support reports, the adjustment strategy is to adjust with the smallest positive step size or the largest negative step size.
[0065] Specifically, if the "access time" of the report is earlier than the "completion time", it indicates that the report has not met the expectations of the business department. In this case, the start time of the scheduling task needs to be adjusted in a positive direction according to the "Adjustment Strategy for Report Task Scheduling" (see Table 5) to ensure that the needs of more users are met as much as possible and improve the satisfaction of the platform service.
[0066] If the "access time" of a report is later than the "completion time," it indicates that the report has not met the expectations of the business department. In this case, the start time of the scheduled task needs to be negatively adjusted according to the "Adjustment Strategy for Report Task Scheduling" to ensure that it does not compete for resources with important reports and improve the satisfaction of platform services. This includes the following situations:
[0067] A. Key Support Reports: Reports with low production costs and high access demand, where service can be improved with relatively low costs, using adjustment strategies with the largest positive step size or the smallest negative step size.
[0068] B. Important Support Reports: High production costs and high access demand result in high costs but large access volumes. Adjust the scheduling strategy by shortening the positive step size or increasing the negative step size.
[0069] C. Secondary assurance report: Production costs are low, access demand is low, and both consumption costs and access volume are not large. Continue to adjust the scheduling strategy by shortening the positive step size or increasing the negative step size.
[0070] D. General Assurance Report: High production costs and low access demand result in high costs but low access volume. Adjustment strategy is to use the smallest positive step or the largest negative step.
[0071] The adjustment strategy for its report task scheduling is shown in Table 5.
[0072] Table 5
[0073] Report hierarchy Access requirements Production costs Task scheduling adjustment strategy 1. Prioritize reporting high Low Scheduling time adjustment: Positive direction +30 minutes, Negative direction -5 minutes 2. Important Guarantee Reports high high Scheduling time adjustment: Positive direction +20 minutes, Negative direction -10 minutes 3. Secondary Guarantee Report Low Low Scheduling time adjustment: Positive direction +10 minutes, Negative direction -20 minutes 4. General Guarantee Report Low high Scheduling time adjustment: Positive direction +5 minutes, Negative direction -30 minutes
[0074] By continuously iterating and adjusting the scheduling strategy of report tasks based on real daily operation log data, the scheduling strategy will gradually and automatically adapt to user behavior, transforming from "passive" operation to "proactive" operation, and maximizing user satisfaction with the reporting system.
[0075] According to the report task scheduling method of the present invention, situations in which the report system fails to satisfy users can be detected in a timely manner, and the report task scheduling configuration can be intelligently adjusted according to user behavior to improve system service satisfaction.
[0076] Figure 3 A schematic diagram of the structure of a report task scheduling device provided in an embodiment of the present invention is shown, as follows: Figure 3 As shown, the report task scheduling device provided in this embodiment of the invention includes: an acquisition module 310, a feature acquisition module 320, a priority determination module 330, and a task scheduling module 340, wherein:
[0077] Module 310 is used to obtain the production logs and access logs of the report;
[0078] Feature acquisition module 320 is used to obtain relevant feature data of the report based on the production log and access log of the report;
[0079] The priority determination module 330 is used to obtain the adjustment priority of the scheduling task of the report based on the relevant feature data of the report;
[0080] The task scheduling module 340 is used to adjust the priority of the scheduled task and the access time of the report based on the report, and adjust the start time of the scheduled task according to the corresponding adjustment strategy.
[0081] According to the report task scheduling device of the present invention, it can promptly detect situations where the report system fails to satisfy users, and intelligently adapt the report task scheduling configuration to user behavior, thereby improving system service satisfaction.
[0082] It should be noted that the specific implementation of the report task scheduling device in this embodiment of the invention is similar to the specific implementation of the report task scheduling method in this embodiment of the invention. For details, please refer to the description in the method section. In order to reduce redundancy, the specific details will not be repeated here.
[0083] Based on the same inventive concept, another embodiment of the present invention provides an electronic device, see [link to previous document]. Figure 4 The electronic device specifically includes the following components: processor 401, memory 402, communication interface 403, and communication bus 404;
[0084] The processor 401, memory 402, and communication interface 403 communicate with each other through the communication bus 404; the communication interface 403 is used to realize information transmission between the devices.
[0085] The processor 401 is used to call the computer program in the memory 402. When the processor executes the computer program, it implements all the steps of the above-described report task scheduling method. For example, when the processor executes the computer program, it implements the following steps: obtaining the production log and access log of the report; obtaining relevant feature data of the report based on the production log and access log of the report; obtaining the adjustment priority of the report's scheduling task according to the relevant feature data of the report; and adjusting the start time of the scheduling task according to the adjustment priority of the report's scheduling task and the access time of the report using the corresponding adjustment strategy.
[0086] Based on the same inventive concept, another embodiment of the present invention provides a non-transitory computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements all the steps of the above-described report task scheduling method. For example, when the processor executes the computer program, it implements the following steps: obtaining the production log and access log of the report; obtaining relevant feature data of the report based on the production log and access log; obtaining the adjustment priority of the report's scheduling task according to the relevant feature data; and adjusting the start time of the scheduling task according to the adjustment priority of the report's scheduling task and the report's access time using a corresponding adjustment strategy.
[0087] Furthermore, the logical instructions in the aforementioned memory can be implemented as software functional units and sold or used as independent products, and can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0088] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of the embodiments of the present invention according to actual needs. Those skilled in the art can understand and implement this without any creative effort.
[0089] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the indicator monitoring method described in various embodiments or some parts of embodiments.
[0090] Furthermore, in this invention, terms such as "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.
[0091] Furthermore, in this invention, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0092] Furthermore, in the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Furthermore, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.
[0093] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A method for scheduling report tasks, characterized in that, include: Retrieve the production logs and access logs for the report; Based on the production logs and access logs of the report, relevant feature data of the report are obtained; The relevant feature data of the report includes at least the production cost feature data and the access demand feature data of the report; the production cost feature data includes the calculation resource weight, the time consumption weight, and the completion time point, and the access demand feature data includes the access frequency weight and the access time point; Based on the relevant feature data of the report, the adjustment priority of the scheduling task of the report is obtained; Based on the adjustment priority of the scheduling task according to the report and the access time of the report, the start time of the scheduling task is adjusted according to the corresponding adjustment strategy. The access demand characteristic data includes the access frequency weight and access time points related to the report; The step of obtaining the adjustment priority of the scheduling task for the report based on the relevant feature data of the report includes: Based on the computational resource weight, time consumption weight, and completion time, the production cost factor is obtained; Based on the access frequency weight and access time point, the access demand factor is obtained; Based on the production cost factor and the access demand factor, the adjustment priority of the scheduling task for the report is obtained.
2. The report task scheduling method according to claim 1, characterized in that, The access demand factor = access frequency weight / overall access frequency weight; the production cost factor = calculation resource weight * 50% + time consumption weight / overall time consumption weight * 50%.
3. The report task scheduling method according to claim 1 or 2, characterized in that, The adjustment of the priority of the report-based scheduling task and the report access time, and the adjustment of the start time of the scheduling task according to the corresponding adjustment strategy, include: If the access time of the report is earlier than the completion time, the start time of the report's scheduling task will be adjusted positively; otherwise, the start time of the report's scheduling task will be adjusted negatively.
4. The report task scheduling method according to claim 3, characterized in that, The priority of the scheduling tasks for the reports includes Level 1 key support reports, Level 2 important support reports, Level 3 secondary support reports, and Level 4 general support reports.
5. The report task scheduling method according to claim 4, characterized in that, If the report access time is earlier than the completion time, the start time of the report's scheduling task is adjusted positively; otherwise, the start time of the report's scheduling task is adjusted negatively, including: For Level 1 key protection reports, adjustments are made using an adjustment strategy that maximizes the positive step size or minimizes the negative step size. For critical support reports at Level 2, adjust the scheduling strategy by shortening the positive step size or increasing the negative step size. For Level 3 secondary support reports, continue to adjust the scheduling strategy by shortening the positive step size or increasing the negative step size; For Level 4 general protection reports, adjustments are made using the smallest positive step size or the largest negative step size adjustment strategy.
6. A report task scheduling device, characterized in that, include: The acquisition module is used to acquire the production logs and access logs of the reports; The feature acquisition module is used to obtain relevant feature data of the report based on the production log and access log of the report; the relevant feature data of the report includes at least the production cost feature data of the report and the access demand feature data of the report; the production cost feature data includes the calculation resource weight, the time consumption weight and the completion time point, and the access demand feature data includes the access frequency weight and the access time point; The priority determination module is used to determine the adjustment priority of the scheduling task of the report based on the relevant feature data of the report; The task scheduling module is used to adjust the priority of the scheduled tasks based on the reports and the access time of the reports, and adjust the start time of the scheduled tasks according to the corresponding adjustment strategy. The access demand characteristic data includes the access frequency weight and access time points related to the report; The step of obtaining the adjustment priority of the scheduling task for the report based on the relevant feature data of the report includes: Based on the computational resource weight, time consumption weight, and completion time, the production cost factor is obtained; Based on the access frequency weight and access time point, the access demand factor is obtained; Based on the production cost factor and the access demand factor, the adjustment priority of the scheduling task for the report is obtained.
7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the report task scheduling method according to any one of claims 1 to 5.
8. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the report task scheduling method according to any one of claims 1 to 5.
Citation Information
Patent Citations
Report scheduling method and device
CN111125097A
Report data pushing method and device
CN112583915A