Method, system and device for determining job priority and storage medium
By automatically obtaining and parsing job information, and calculating job priorities with dependencies and configuration parameters, the problem of inefficient manual configuration in the existing technology and inability to respond to job dependencies changes in real time, achieving efficient and accurate job priority management.
Patent Information
- Application Number
- CN202510365875.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-26
- Publication Date
- 2025-06-06
AI Technical Summary
In the prior art, the priority configuration of offline batch jobs depends on manual intervention, and there are problems such as inefficiency, easy to cause configuration errors, inability to respond to job dependency changes in real time, and lack of unified priority evaluation standards.
By obtaining the job information of the target job, analyzing its dependencies, and calculating the priority of the job with configuration parameters, automatic configuration and dynamic adjustment of priority are achieved.
It improves the accuracy and efficiency of job priority configuration, avoids the subjectivity and error of manual configuration, dynamically adapts to changes in job dependencies, and ensures timely execution of key jobs.
Smart Images
Figure CN120104285A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, and in particular to a method, system, device and storage medium for determining job priority. Background Art
[0002] With the rapid development of big data processing technology and the in-depth advancement of enterprise digital transformation, the offline batch processing job scheduling system, as a core component of the data processing platform, has a direct impact on the timeliness of data output and the accuracy of business decisions. However, in current technical practice, the priority configuration of offline batch processing jobs still generally adopts manual intervention, which can no longer meet the complex needs of modern enterprise data processing.
[0003] In existing technical solutions, the setting of job priorities mainly relies on the manual judgment and experience accumulation of system administrators. This manual configuration mechanism has the following technical limitations: First, in the face of large-scale job scheduling scenarios, manual configuration is inefficient and prone to configuration errors due to human negligence, affecting system stability; second, it is unable to respond to changes in job dependencies in real time. When the job topology changes, manual adjustments have significant time lags, making it difficult to ensure the timely execution of critical path jobs; third, there is a lack of unified priority evaluation standards, and the configuration strategies of different administrators may differ significantly, resulting in uneven allocation of system resources. Summary of the invention
[0004] Based on the above problems, the present application provides a method, system, device and storage medium for determining job priority, with the aim of improving the accuracy and effectiveness of job priority configuration.
[0005] The embodiments of the present application disclose the following technical solutions:
[0006] A first aspect of the present application provides a method for determining a job priority, the method comprising:
[0007] Obtaining job information of a target job; the job information includes dependencies and configuration parameters of the target job;
[0008] Determine the upstream job of the target job and its dependency level according to the dependency relationship; the dependency level is the level to which the upstream job of the target job belongs;
[0009] Determine a corresponding computing cardinality and a corresponding computing increment of the target job based on the dependency level and the configuration parameters;
[0010] Calculating the priority of the target job based on the corresponding calculation cardinality and the corresponding calculation increment of the target job;
[0011] The priority of the target job is written back to the job table.
[0012] In an optional implementation, the configuration parameters include a calculation cardinality and a key job identifier; and determining a corresponding calculation cardinality and a corresponding calculation increment of the target job based on the dependency level and the configuration parameters includes:
[0013] Determine the corresponding computing cardinality of the target job based on the computing cardinality configuration state in the configuration parameters;
[0014] A computation increment corresponding to the target job is determined based on the dependency level and the key job identifier.
[0015] In an optional implementation, the determining the corresponding computing cardinality of the target job based on the computing cardinality configuration state in the configuration parameters includes:
[0016] When the calculation base is not configured in the configuration parameters, the calculation base corresponding to the target job is the preset basic calculation base;
[0017] When a computing base has been configured in the configuration parameters, the computing base corresponding to the target job is the computing base configured in the configuration parameters.
[0018] In an optional implementation, the calculation increment includes a first calculation increment and a second calculation increment; when the dependency levels are the same, the first calculation increment is smaller than the second calculation increment; the key job identifier includes a first identifier and a second identifier; the first identifier indicates that the target job is a non-key job; the second identifier indicates that the target job is a key job; the determining of the corresponding calculation increment of the target job based on the dependency level and the key job identifier includes:
[0019] When the key job identifier is the first identifier, the corresponding calculation increment of the target job is the first calculation increment corresponding to the dependency level;
[0020] When the key job identifier is the second identifier, the corresponding calculation increment of the target job is the second calculation increment corresponding to the dependency level.
[0021] In an optional implementation, the configuration parameters further include a job calculation identifier; the job calculation identifier indicates whether the target job participates in priority calculation; before determining the corresponding calculation cardinality and the corresponding calculation increment of the target job based on the dependency hierarchy and the configuration parameters, determining the job priority further includes:
[0022] According to the job calculation identifier in the job information, the jobs that do not participate in the priority calculation in the target job are filtered.
[0023] In an optional implementation, before obtaining the job information of the target job, the method for determining the job priority further includes:
[0024] The job table is scanned periodically based on a preset time interval to filter out target jobs; the target jobs are jobs whose status in the job table has changed.
[0025] In an optional implementation, writing the priority of the target job back to the job table includes:
[0026] Deduplication processing is performed on the priority of the target job;
[0027] Taking the maximum value of the priority after deduplication processing to obtain the target priority;
[0028] The target priority is written back to the job table.
[0029] A second aspect of the present application provides a system for determining a job priority, the system comprising:
[0030] A job information acquisition module, used to acquire job information of a target job; the job information includes dependencies and configuration parameters of the target job;
[0031] A dependency determination module, used to determine the upstream job of the target job and its dependency level according to the dependency relationship; the dependency level is the level to which the upstream job of the target job belongs;
[0032] A computing parameter determination module, used to determine a corresponding computing cardinality and a corresponding computing increment of the target job based on the dependency level and the configuration parameters;
[0033] A priority calculation module, used to calculate the priority of the target job based on the corresponding calculation base and the corresponding calculation increment of the target job;
[0034] The priority writing back module is used to write the priority of the target job back to the job table.
[0035] A third aspect of the present application provides a device for determining a job priority, the device comprising: a processor and a memory:
[0036] The memory is used to store program code and transmit the program code to the processor;
[0037] The processor is used to execute the steps of the method for determining job priority introduced in any implementation of the first aspect according to the instructions in the program code.
[0038] A fourth aspect of the present application provides a computer-readable storage medium for storing program code, wherein the program code is used to execute the steps of the method for determining job priority introduced in any implementation of the first aspect.
[0039] Compared with the prior art, this application has the following beneficial effects:
[0040] In the technical solution of the present application, the job information of the target job is first obtained; then, the upstream job of the target job and its dependency hierarchy are determined according to the dependency relationship; then, the corresponding calculation cardinality and corresponding calculation increment of the target job are determined based on the dependency hierarchy and the configuration parameters; then, the priority of the target job is calculated based on the corresponding calculation cardinality and corresponding calculation increment of the target job; finally, the priority of the target job is written back to the job table. In the technical solution of the present application, by automatically obtaining job information, parsing dependencies, and calculating priorities in combination with configuration parameters, and finally writing the results back to the job table, the whole process automation of priority configuration is realized, thereby improving the efficiency and accuracy of priority management, avoiding the subjectivity and errors of manual configuration, and dynamically adapting to changes in job dependencies, thereby ensuring the timely execution of key jobs. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.
[0042] Figure 1 A flow chart of a method for determining job priority provided in an embodiment of the present application;
[0043] Figure 2 A dependency diagram provided for an embodiment of the present application;
[0044] Figure 3 A flowchart of another method for determining job priority provided in an embodiment of the present application;
[0045] Figure 4 A schematic diagram of the structure of a system for determining job priority provided in an embodiment of the present application. DETAILED DESCRIPTION
[0046] As described above, the current job priority configuration mainly relies on manual settings, which has problems such as low efficiency, poor adaptability, and difficulty in dynamically responding to changes in job dependencies.
[0047] After research, the inventors have proposed a method, system, device and storage medium for determining job priority.
[0048] First, the job information of the target job is obtained; then, the upstream job of the target job and its dependency hierarchy are determined according to the dependency relationship; then, the corresponding calculation cardinality and the corresponding calculation increment of the target job are determined based on the dependency hierarchy and the configuration parameters; then, the priority of the target job is calculated based on the corresponding calculation cardinality and the corresponding calculation increment of the target job; finally, the priority of the target job is written back to the job table.
[0049] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0050] See also Figure 1 , which is a flow chart of a method for determining job priority provided by an embodiment of the present application. Figure 1 As shown, the method comprises the following steps:
[0051] S101: Obtain job information of a target job.
[0052] In the embodiment of the present application, the target job refers to a job that needs to be re-prioritized. In order to re-prioritize it, it is first necessary to obtain the job information of the target job, and the job information includes the dependency relationship and configuration parameters of the target job.
[0053] Dependencies refer to other jobs that the target job needs to rely on before or during execution. These dependent jobs are critical to the successful execution of the target job. For example, if the target job is a data processing task, it may depend on the completion of one or more data preparation tasks. These data preparation tasks may be data cleaning, data conversion, or data loading.
[0054] Configuration parameters are specific configurations that need to be followed when determining job priorities.
[0055] In one example implementation, the job information may be obtained from a job table.
[0056] S102: Determine the upstream job of the target job and its dependency level according to the dependency relationship.
[0057] In an embodiment of the present application, based on the dependency relationship of the target job in the job information obtained in the previous step, the upstream jobs of the target job (ie, the jobs that the target job needs to depend on before execution) and the dependency levels of these upstream jobs are determined.
[0058] For example, suppose the target job is "data processing A", which depends on two upstream jobs, "data cleaning B" and "data conversion C". Furthermore, "data cleaning B" also depends on "data extraction D". Among them, "data extraction D" is the upstream job of "data cleaning B". The dependency hierarchy of each upstream job can be determined by traversing the dependency relationship.
[0059] Figure 2 This is a dependency diagram for this example. Figure 2 As shown, the target job "data processing A" is at the first level, its upstream jobs "data cleaning B" and "data conversion C" are at the second level ("data conversion C" has no dependency on "data cleaning B"), and the upstream job "data extraction D" of "data cleaning B" is at the third level.
[0060] S103: Determine a corresponding computing cardinality and a corresponding computing increment of the target job based on the dependency level and configuration parameters.
[0061] In an embodiment of the present application, after the upstream job of the target job and its dependency level are determined, the corresponding calculation cardinality and calculation increment of the target job can be determined according to the dependency level and configuration parameters.
[0062] In the embodiment of the present application, the calculation cardinality refers to the starting calculation priority of the job. The value of the calculation cardinality is determined according to the weight allocation of the scheduling job system, and different systems or different job types may have different weight allocations.
[0063] The calculation increment refers to the incremental value of a job when the priority calculation is adjusted. The value of the calculation increment is positively correlated with the dependency level, that is, the higher the dependency level, the larger the value of the calculation increment. In addition, the value of the calculation increment is also positively correlated with the importance of the target job (whether it is a key job). At the same dependency level, the calculation increment value of a key job is larger than that of a non-key job.
[0064] In the embodiment of the present application, the specific value of the calculation increment can be configured and adjusted according to actual conditions and is not specifically limited here.
[0065] In an optional implementation, the configuration parameters include a calculation base and a key job identifier.
[0066] The key operation identifier includes a first identifier and a second identifier. The first identifier indicates that the target operation is a non-key operation, and the second identifier indicates that the target operation is a key operation.
[0067] In an optional implementation, the calculation increment includes a first calculation increment and a second calculation increment. When the dependency levels are the same, the first calculation increment is smaller than the second calculation increment.
[0068] In an example implementation, a configuration parameter table is shown in Table 1, and a correspondence table between dependency levels and calculation increments is shown in Table 2.
[0069] Table 1
[0070]
[0071]
[0072] Table 2
[0073] Dependency Hierarchy Second calculation increment First calculation increment 1-2 5 1 3-4 10 3 5-6 15 6 …… …… ……
[0074] In an embodiment of the present application, the specific steps of determining the corresponding calculation cardinality and the corresponding calculation increment of the target job based on the dependency level and the configuration parameters include:
[0075] Step 1: Determine the corresponding computing cardinality of the target job based on the computing cardinality configuration status in the configuration parameters.
[0076] When the calculation base is not configured in the configuration parameters, the calculation base corresponding to the target job is the preset basic calculation base.
[0077] In the embodiment of the present application, the preset basic calculation base can be 0, or can be set according to the actual application, and is not specifically limited here.
[0078] When the calculation base is configured in the configuration parameters, the calculation base of the target job is the calculation base configured in the configuration parameters.
[0079] Refer to the example configuration parameter table shown in Table 1. Among them, the calculation cardinality is not configured in the configuration parameters of job_A, so the calculation cardinality of job_A is the preset basic calculation cardinality 0. The calculation cardinality is configured in the configuration parameters of job_B, so the calculation cardinality of job_B is the calculation cardinality 20 configured in the configuration parameters.
[0080] Step 2: Determine the corresponding computational increment of the target job based on the dependency hierarchy and key job identifier.
[0081] When the key job identifier is the first identifier, the corresponding calculation increment of the target job is the first calculation increment corresponding to the dependency level.
[0082] When the key job identifier is the second identifier, the corresponding calculation increment of the target job is the second calculation increment corresponding to the dependency level.
[0083] Refer to the example configuration parameter table shown in Table 1, where the key job identifier of job_A is the second identifier, indicating that job_A is a key job, and the corresponding calculation increment of job_A is the second calculation increment corresponding to the dependency level. Assuming that the dependency level of job_A is 3, refer to the example dependency level and calculation increment correspondence table shown in Table 2, the corresponding calculation increment of job_A is 10. The key job identifier of job_B is the first identifier, indicating that job_B is a non-key job, and the corresponding calculation increment of job_B is the first calculation increment corresponding to the dependency level. Assuming that the dependency level of job_B is 5, refer to the example dependency level and calculation increment correspondence table shown in Table 2, the corresponding calculation increment of job_B is 6.
[0084] S104: Calculate the priority of the target job based on the corresponding calculation cardinality and corresponding calculation increment of the target job.
[0085] In the embodiment of the present application, the priority of the target job may be calculated by the calculation base and calculation increment corresponding to the target job determined in the previous step.
[0086] In the embodiment of the present application, the priority of the target job can be calculated by the following formula:
[0087] The priority of the target job = calculation base + calculation increment.
[0088] Referring to the above example, the priority of job_A=0+10=10, and the priority of job_B=20+6=26.
[0089] S105: Write the priority of the target job back to the job table.
[0090] In an embodiment of the present application, the priority of the target job determined in the previous step is written back to the job table so that the scheduling system can arrange the execution order of the jobs according to the priority.
[0091] In an exemplary implementation, a field in the job table (such as a “priority” field) may be updated to reflect the new priority value.
[0092] In the above example, the priority of job_A is updated to 10, the priority of job_B is updated to 26, and they are written back to the job table. In this way, when the scheduling system runs next time, it will arrange the execution order of job_A and job_B according to this new priority value.
[0093] In the embodiment of the present application, by automatically acquiring job information, parsing dependencies, and calculating priorities in combination with configuration parameters, and finally writing the results back to the job table, full-process automation of priority configuration is achieved, thereby improving the efficiency and accuracy of priority management, avoiding the subjectivity and errors of manual configuration, and dynamically adapting to changes in job dependencies, thereby ensuring the timely execution of key jobs.
[0094] Figure 3 Another method flow chart for determining job priority provided in an embodiment of the present application. In the embodiment introduced by this figure, a more detailed description is provided for the implementation of the method for determining job priority.
[0095] S301 : Periodically scan a job table based on a preset time interval to filter out target jobs.
[0096] In the embodiment of the present application, the target job is a job whose status has changed in the job table.
[0097] Scan the job table at a preset time interval (for example, every 10 minutes) to filter out target jobs whose status has changed. Such jobs need to recalculate the job priority.
[0098] In an example implementation, the status change can be realized by detecting the updateTime field in the job table. If the updateTime is greater than the last scan timestamp, the job is determined to be the target job. For example, the system scans the job table at 2024-10-01 12:00:00 and selects jobs with updateTime greater than 2024-10-01 11:50:00 as target jobs.
[0099] S302: Obtain job information of the target job.
[0100] S303: Determine the upstream job of the target job and its dependency level according to the dependency relationship.
[0101] S302-S303 are implemented in substantially the same manner as S101-S102 in the method embodiment described above, and will not be elaborated here. For related technical implementations, reference may be made to the description of S101-S102 described above.
[0102] S304: Filter the target jobs that do not participate in priority calculation according to the job calculation identifier in the job information.
[0103] In the embodiment of the present application, the configuration parameters also include a job calculation identifier, which indicates whether the target job participates in priority calculation.
[0104] In the job scheduling system, there are some jobs that are manually prioritized. The priorities of these jobs will not be affected by the system's automatic priority calculation logic. For example, for some critical tasks that need to be executed first, the administrator may manually set their priorities to ensure that they can be processed first when resources are tight or the system is busy. Therefore, before performing the priority calculation, it is necessary to eliminate such jobs that do not participate in the priority calculation.
[0105] In an exemplary implementation, another configuration parameter table is shown in Table 3. Figure 3 As shown in the figure, since the job calculation mark of job_C is not involved in the calculation, it needs to be removed from the target job table.
[0106] Table 3
[0107] Job Name Job calculation identifier Key Operations Marking Calculating Cardinality job_A Participate in calculation Second mark / job_B Participate in calculation First logo 20 job_C Not included in calculation First logo / …… …… …… ……
[0108] S305: Determine a corresponding computing cardinality and a corresponding computing increment of the target job based on the dependency level and configuration parameters.
[0109] S306: Calculate the priority of the target job based on the corresponding calculation cardinality and corresponding calculation increment of the target job.
[0110] S305-S306 are implemented in substantially the same manner as S103-S104 in the method embodiment described above, and will not be elaborated here. For related technical implementations, reference may be made to the above description of S103-S104.
[0111] S307: De-duplicate the priority of the target job.
[0112] In an optional implementation, after the previous step is completed, the at least one priority result obtained can be stored in a temporary storage area. The temporary storage area can be a data structure in memory (such as a list, a dictionary, or a temporary table in a database connection pool), or a temporary file on a disk or a dedicated temporary table in a database.
[0113] In an embodiment of the present application, due to the complexity of the dependency relationship, the same job may be dependent on multiple downstream jobs with different dependency levels. The priority calculated in the previous step may result in multiple priority results for one job. Therefore, it is necessary to deduplicate the multiple priority results calculated in the previous step to ensure that only one priority calculation result of the same target job is retained. For example, if the priority calculation result of the target job is [50,50,70], the priority after deduplication is [50,70].
[0114] S308 , taking the maximum value of the priority after deduplication processing to obtain the target priority.
[0115] In the embodiment of the present application, the maximum value is selected from the priorities after deduplication as the target priority to ensure that the most important job can obtain the highest priority. For example, if the priorities after deduplication are [50, 70], the target priority is 70.
[0116] S309: Write the target priority back to the job table.
[0117] In an embodiment of the present application, the target priority obtained in the previous step is written back into the job table so that the scheduling system can arrange the execution order of the jobs according to the priority.
[0118] In an exemplary implementation, a field in the job table (such as a “priority” field) may be updated to reflect the new priority value.
[0119] In an embodiment of the present application, by periodically scanning the job table and filtering out the target job based on the state change, the job that needs to recalculate the priority is effectively identified. By introducing the job calculation identifier, the jobs that do not participate in the automatic priority calculation are successfully filtered out, ensuring the reasonable allocation of resources. The priority is calculated based on the dependency hierarchy and configuration parameters, which not only takes into account the dependency relationship between jobs, but also incorporates business logic and special needs, thereby improving the accuracy and flexibility of job priority determination. Deduplication and maximum value processing further streamline the priority results, ensure the simplicity and rationality of the priority results, and ensure that key jobs are executed first. The updated priority is written back to the job table in real time, providing the scheduling system with a real-time and accurate priority basis, thereby improving the overall job processing efficiency. The embodiment of the present application significantly improves the accuracy and effectiveness of job priority configuration by automatically calculating job priorities.
[0120] Based on the method for determining job priority provided in the aforementioned embodiment, the present application also provides a system for determining job priority. Figure 4 A schematic diagram of a system for determining job priority provided in an embodiment of the present application. Figure 4 As shown, the system for determining the job priority includes: a job information acquisition module 401 , a dependency determination module 402 , a calculation parameter determination module 403 , a priority calculation module 404 and a priority write-back module 405 .
[0121] The job information acquisition module 401 is used to acquire the job information of the target job; the job information includes the dependency relationship and configuration parameters of the target job.
[0122] The dependency determination module 402 is used to determine the upstream job of the target job and its dependency level according to the dependency relationship; the dependency level is the level to which the upstream job of the target job belongs.
[0123] The computing parameter determination module 403 is used to determine the corresponding computing cardinality and the corresponding computing increment of the target job based on the dependency level and the configuration parameters.
[0124] The priority calculation module 404 is used to calculate the priority of the target job based on the corresponding calculation cardinality and corresponding calculation increment of the target job.
[0125] The priority writing back module 405 is used to write the priority of the target job back to the job table.
[0126] The embodiment of the present application realizes the full process automation of priority configuration by combining the functions of the job information acquisition module 401, the dependency determination module 402, the calculation parameter determination module 403, the priority calculation module 404 and the priority write-back module 405, thereby improving the efficiency and accuracy of priority management, avoiding the subjectivity and errors of manual configuration, and dynamically adapting to changes in job dependencies, thereby ensuring the timely execution of key jobs.
[0127] In an optional implementation, the configuration parameters include a calculation base and a key operation identifier. The calculation parameter determination module 403 includes: a calculation base determination module and a calculation increment determination module.
[0128] The computing cardinality determination module is used to determine the computing cardinality corresponding to the target job based on the computing cardinality configuration state in the configuration parameters.
[0129] The computing increment determination module is used to determine the computing increment corresponding to the target job based on the dependency level and the key job identifier.
[0130] In an optional implementation, the calculation cardinality determination module is specifically used to:
[0131] When the calculation base is not configured in the configuration parameters, the calculation base of the target job is the preset basic calculation base;
[0132] When the calculation base is configured in the configuration parameters, the calculation base of the target job is the calculation base configured in the configuration parameters.
[0133] In an optional implementation, the calculation increment includes a first calculation increment and a second calculation increment. When the dependency levels are the same, the first calculation increment is smaller than the second calculation increment.
[0134] The key operation identifier includes a first identifier and a second identifier. The first identifier indicates that the target operation is a non-key operation, and the second identifier indicates that the target operation is a key operation.
[0135] In an optional implementation, the calculation increment determination module is specifically used to:
[0136] When the key job identifier is the first identifier, the corresponding calculation increment of the target job is the first calculation increment corresponding to the dependency level;
[0137] When the key job identifier is the second identifier, the corresponding calculation increment of the target job is the second calculation increment corresponding to the dependency level.
[0138] In an optional implementation, the configuration parameters further include a job calculation identifier, which indicates whether the target job participates in priority calculation.
[0139] In an optional implementation, the system for determining job priority further includes: a filtering module, configured to filter jobs that do not participate in priority calculation in the target job according to the job calculation identifier in the job information.
[0140] In an optional implementation, the system for determining job priority further includes: a target job screening module for periodically scanning the job table based on a preset time interval to screen out target jobs; the target jobs are jobs whose status has changed in the job table.
[0141] In an optional implementation, the priority write-back module 405 is specifically configured to:
[0142] De-duplicate the priority of the target job;
[0143] The maximum value of the priority after deduplication processing is taken to obtain the target priority;
[0144] Write the target priority back to the job table.
[0145] In addition, an embodiment of the present application further provides a device for determining a job priority, wherein the device for determining a job priority includes a processor and a memory.
[0146] The memory is used to store program code and transmit the program code to the processor;
[0147] The processor is used to execute the steps of the method for determining the job priority described in any of the above method embodiments according to the instructions in the program code.
[0148] In addition, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. When the program is executed by a processor, the method for determining the job priority as described in any of the method embodiments is implemented.
[0149] It should be noted that each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments. The device and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components indicated as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.
[0150] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A method for determining job priority, characterized in that: include: Get the job information of the target job; The job information includes dependencies and configuration parameters of the target job; Determine the upstream job of the target job and its dependency level according to the dependency relationship; The dependent level is the level to which the upstream job of the target job belongs; Determine a corresponding computing cardinality and a corresponding computing increment of the target job based on the dependency level and the configuration parameters; Calculating the priority of the target job based on the corresponding calculation cardinality and the corresponding calculation increment of the target job; The priority of the target job is written back to the job table.
2. The method according to claim 1, characterized in that: The configuration parameters include a calculation cardinality and a key job identifier; the determining a corresponding calculation cardinality and a corresponding calculation increment of the target job based on the dependency level and the configuration parameters includes: Determine the corresponding computing cardinality of the target job based on the computing cardinality configuration state in the configuration parameters; A computation increment corresponding to the target job is determined based on the dependency level and the key job identifier.
3. The method according to claim 2, characterized in that The determining the corresponding computing cardinality of the target job based on the computing cardinality configuration state in the configuration parameters includes: When the calculation base is not configured in the configuration parameters, the calculation base corresponding to the target job is the preset basic calculation base; When a computing base has been configured in the configuration parameters, the computing base corresponding to the target job is the computing base configured in the configuration parameters.
4. The method according to claim 2, characterized in that: The calculation increment includes a first calculation increment and a second calculation increment; when the dependency levels are the same, the first calculation increment is smaller than the second calculation increment; the key operation identifier includes a first identifier and a second identifier; The first identifier indicates that the target operation is a non-key operation; The second identifier indicates that the target job is a key job; and determining the corresponding calculation increment of the target job based on the dependency level and the key job identifier includes: When the key job identifier is the first identifier, the corresponding calculation increment of the target job is the first calculation increment corresponding to the dependency level; When the key job identifier is the second identifier, the corresponding calculation increment of the target job is the second calculation increment corresponding to the dependency level.
5. The method according to claim 1, characterized in that The configuration parameters also include a job calculation identifier; the job calculation identifier indicates whether the target job participates in priority calculation; Before determining the corresponding computing cardinality and the corresponding computing increment of the target job based on the dependency level and the configuration parameters, the method further includes: According to the job calculation identifier in the job information, the jobs that do not participate in the priority calculation in the target job are filtered.
6. The method according to claim 1, characterized in that Before obtaining the job information of the target job, the method further includes: The job table is scanned periodically based on a preset time interval to filter out target jobs; the target jobs are jobs whose status in the job table has changed.
7. The method according to claim 1, characterized in that Writing the priority of the target job back to the job table includes: Deduplication processing is performed on the priority of the target job; Taking the maximum value of the priority after deduplication processing to obtain the target priority; The target priority is written back to the job table.
8. A system for determining job priorities, characterized in that: The system comprises: A job information acquisition module, used to acquire job information of a target job; the job information includes dependencies and configuration parameters of the target job; A dependency determination module, used to determine the upstream job of the target job and its dependency level according to the dependency relationship; the dependency level is the level to which the upstream job of the target job belongs; A computing parameter determination module, used to determine a corresponding computing cardinality and a corresponding computing increment of the target job based on the dependency level and the configuration parameters; A priority calculation module, used to calculate the priority of the target job based on the corresponding calculation base and the corresponding calculation increment of the target job; The priority writing back module is used to write the priority of the target job back to the job table.
9. A device for determining job priority, characterized in that: include: Processor and memory: The memory is used to store program code and transmit the program code to the processor; The processor is configured to execute the steps of the method for determining job priority according to any one of claims 1 to 7 according to the instructions in the program code.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store program codes, and the program codes are used to execute the steps of the method for determining job priorities according to any one of claims 1 to 7.