Resource quantitative evaluation method and device, computer equipment and readable storage medium

Abstract

The invention relates to a performance test method and device, computer equipment and a readable storage medium. The method comprises the following steps: acquiring metadata information and preset transaction index information of a to-be-tested system; according to a preset resource quantification strategy, preset transaction index information and metadata information, performing quantification calculation on a system resource demand corresponding to the to-be-tested system to obtain a target total memory result; the target total memory result comprises a data memory result, a service concurrent memory result and a security buffer memory result; and determining a target system resource based on the data memory result, the service concurrent memory result and the security buffer memory result, and performing resource allocation on the to-be-tested system according to the target system resource. By adopting the method, the accuracy of resource allocation can be improved.

Description

Technical Field

[0001] This application relates to the field of resource assessment technology, and in particular to a resource quantification assessment method, apparatus, computer equipment, and readable storage medium. Background Technology

[0002] With the development of financial business in the financial sector, the business systems need to process more and more business data, which in turn requires frequent performance testing of the business systems. Before conducting performance testing, test resources need to be allocated to the system under test.

[0003] In traditional techniques, for a system under test, architects and other developers use their experience to assess the system resource requirements of a certain type of system under test, determine the target system resources required for that type of system under test, and then allocate resources for each subsequent system under test of the same type based on the fixed target system resources.

[0004] However, traditional technologies allocate resources based on fixed target system resources, which leads to a mismatch between target system resources and system resource requirements, resulting in poor accuracy in resource allocation. Summary of the Invention

[0005] Therefore, it is necessary to provide a resource quantification assessment method, apparatus, computer equipment, and readable storage medium to address the aforementioned technical problems.

[0006] Firstly, this application provides a method for quantitative assessment of resources, including:

[0007] Obtain metadata and preset transaction metrics information of the system under test;

[0008] The system resource requirements of the system under test are quantified and calculated based on the preset resource quantification strategy, the preset transaction indicator information, and the metadata information to obtain the target total memory result; the target total memory result includes data memory result, business concurrency memory result, and safety buffer memory result;

[0009] Based on the data memory results, the business concurrency memory results, and the security buffer memory results, the target system resources are determined, and the system under test is allocated resources according to the target system resources.

[0010] In one embodiment, the metadata information includes database table metadata information; the step of quantifying the system resource requirements corresponding to the system under test based on a preset resource quantification strategy, the preset transaction indicator information, and the metadata information to obtain the target total memory result includes:

[0011] The data memory result is obtained by calculating based on the database table metadata information and the preset expansion coefficient;

[0012] The business concurrency memory result is obtained by calculating based on the preset transaction index information;

[0013] The data memory result and the business concurrency memory result are analyzed and calculated based on the preset buffer threshold to determine the safe buffer memory result.

[0014] In one embodiment, the database table metadata information includes the number of database tables, the average number of fields per table, and the average field length; the calculation based on the database table metadata information and a preset expansion coefficient to obtain the data memory result includes:

[0015] The initial data memory result is determined based on the number of database tables, the average number of fields per table, and the average field length.

[0016] The initial data memory result is corrected and calculated based on a preset expansion coefficient to obtain the data memory result.

[0017] In one embodiment, the preset transaction metric information includes peak transaction concurrency, average transaction processing time, and single transaction memory overhead; the step of calculating the business concurrency memory result based on the preset transaction metric information includes:

[0018] The concurrent memory status of the system under test is quantitatively calculated based on the peak transaction concurrency, the average transaction processing time, and the single transaction memory overhead to obtain the business concurrent memory result.

[0019] In one embodiment, the target system resources further include the target number of processor cores and the target storage space; determining the target system resources based on the data memory result, the service concurrency memory result, and the security buffer memory result includes:

[0020] Obtain incremental data information and determine the total amount of data to be stored based on the incremental data information;

[0021] The target number of processor cores is determined based on the preset transaction indicator information, and the target storage space is determined based on the total amount of data storage.

[0022] The target system resources are determined based on the data memory results, the business concurrency memory results, the security buffer memory results, the target number of processor cores, and the target storage space.

[0023] In one embodiment, the step of allocating resources to the system under test based on the target system resources includes:

[0024] Based on the system type of the system to be tested, determine the correction coefficient corresponding to the system resource requirements;

[0025] The target system resources are corrected according to the correction coefficient, and resources are allocated according to the corrected target system resources.

[0026] In one embodiment, after allocating resources to the system under test according to the target system resources, the method further includes;

[0027] Based on the performance test results, the preset transaction indicator information, the preset expansion coefficient and the preset buffer threshold in the preset resource quantification strategy are verified to obtain the verification results.

[0028] If the verification result is a verification failure, one or more of the preset transaction indicator information, the preset expansion coefficient, and the preset buffer threshold are adjusted according to the verification result, and a performance test is performed based on the adjusted preset transaction indicator information, the preset expansion coefficient, and the preset buffer threshold to obtain a new performance test result.

[0029] Secondly, this application also provides a resource quantification and assessment device, comprising:

[0030] The acquisition module is used to acquire metadata information and preset transaction indicator information of the system under test.

[0031] The calculation module is used to quantify the system resource requirements of the system under test according to the preset resource quantification strategy, the preset transaction indicator information and the metadata information, and obtain the target total memory result; the target total memory result includes data memory result, business concurrency memory result and safety buffer memory result;

[0032] The allocation module is used to determine the target system resources based on the data memory results, the business concurrency memory results, and the security buffer memory results, and to allocate resources to the system under test according to the target system resources.

[0033] In one embodiment, the metadata information includes database table metadata information; the calculation module is specifically used to calculate based on the database table metadata information and a preset expansion coefficient to obtain the data memory result;

[0034] The business concurrency memory result is obtained by calculating based on the preset transaction index information;

[0035] The data memory result and the business concurrency memory result are analyzed and calculated based on the preset buffer threshold to determine the safe buffer memory result.

[0036] In one embodiment, the database table metadata information includes the number of database tables, the average number of fields per table, and the average field length; the calculation module is specifically used to determine the initial data memory result based on the number of database tables, the average number of fields per table, and the average field length.

[0037] The initial data memory result is corrected and calculated based on a preset expansion coefficient to obtain the data memory result.

[0038] In one embodiment, the preset transaction indicator information includes peak transaction concurrency, average transaction processing time, and single transaction memory overhead; the calculation module is specifically used to quantify the concurrent memory status of the system under test based on the peak transaction concurrency, the average transaction processing time, and the single transaction memory overhead, to obtain the business concurrent memory result.

[0039] In one embodiment, the target system resources further include the target number of processor cores and the target storage space; the allocation module is specifically used to acquire incremental data information and determine the total amount of data storage based on the incremental data information.

[0040] The target number of processor cores is determined based on the preset transaction indicator information, and the target storage space is determined based on the total amount of data storage.

[0041] The target system resources are determined based on the data memory results, the business concurrency memory results, the security buffer memory results, the target number of processor cores, and the target storage space.

[0042] In one embodiment, the allocation module is specifically used to determine the correction coefficient corresponding to the system resource requirements based on the system type of the system to be tested;

[0043] The target system resources are corrected according to the correction coefficient, and resources are allocated according to the corrected target system resources.

[0044] In one embodiment, the device further includes;

[0045] The verification module is used to verify the preset transaction indicator information, the preset expansion coefficient and the preset buffer threshold in the preset resource quantification strategy based on the performance test results, and obtain the verification results.

[0046] An adjustment module is used to adjust one or more of the preset transaction indicator information, the preset expansion coefficient, and the preset buffer threshold according to the verification result if the verification result is a verification failure, and to perform performance testing based on the adjusted preset transaction indicator information, the preset expansion coefficient, and the preset buffer threshold to obtain a new performance test result.

[0047] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0048] Obtain metadata and preset transaction metrics information of the system under test;

[0049] The system resource requirements of the system under test are quantified and calculated based on the preset resource quantification strategy, the preset transaction indicator information, and the metadata information to obtain the target total memory result; the target total memory result includes data memory result, business concurrency memory result, and safety buffer memory result;

[0050] Based on the data memory results, the business concurrency memory results, and the security buffer memory results, the target system resources are determined, and the system under test is allocated resources according to the target system resources.

[0051] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0052] Obtain metadata and preset transaction metrics information of the system under test;

[0053] The system resource requirements of the system under test are quantified and calculated based on the preset resource quantification strategy, the preset transaction indicator information, and the metadata information to obtain the target total memory result; the target total memory result includes data memory result, business concurrency memory result, and safety buffer memory result;

[0054] Based on the data memory results, the business concurrency memory results, and the security buffer memory results, the target system resources are determined, and the system under test is allocated resources according to the target system resources.

[0055] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0056] Obtain metadata and preset transaction metrics information of the system under test;

[0057] The system resource requirements of the system under test are quantified and calculated based on the preset resource quantification strategy, the preset transaction indicator information, and the metadata information to obtain the target total memory result; the target total memory result includes data memory result, business concurrency memory result, and safety buffer memory result;

[0058] Based on the data memory results, the business concurrency memory results, and the security buffer memory results, the target system resources are determined, and the system under test is allocated resources according to the target system resources.

[0059] The aforementioned resource quantification assessment method, apparatus, computer equipment, and readable storage medium acquire metadata information and preset transaction indicator information of the system under test. Based on the preset resource quantification strategy, preset transaction indicator information, and metadata information, the system resource requirements corresponding to the system under test are quantified and calculated to obtain the target total memory result. The target total memory result includes data memory result, business concurrency memory result, and safety buffer memory result. Based on the data memory result, business concurrency memory result, and safety buffer memory result, the target system resources are determined, and resources are allocated to the system under test according to the target system resources. Using this method, by quantifying the system resource requirements of the system under test according to the dimensions of data memory result, business concurrency memory result, and safety buffer memory result through a preset resource quantification strategy, the accuracy of resource requirement quantification can be improved, ensuring that the target system resources match the resource requirements of the system under test. Furthermore, allocating resources to the system under test using the target system resources determined by the data memory result, business concurrency memory result, and safety buffer memory result can improve the accuracy of resource allocation. Attached Figure Description

[0060] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0061] Figure 1 This is a flowchart illustrating the resource quantification and evaluation process in one embodiment;

[0062] Figure 2 This is a flowchart illustrating the calculation of data memory results, business concurrency memory results, and safety buffer memory results in one embodiment.

[0063] Figure 3 This is a flowchart illustrating the process of calculating data memory results in one embodiment;

[0064] Figure 4 This is a flowchart illustrating the process of determining target system resources in one embodiment;

[0065] Figure 5 This is a flowchart illustrating the process of correcting target system resources based on a correction factor in one embodiment.

[0066] Figure 6 This is a flowchart illustrating deviation analysis based on verification results in one embodiment;

[0067] Figure 7 This is a flowchart illustrating an example of a resource quantification and assessment method in one embodiment;

[0068] Figure 8 This is a structural block diagram of a resource quantification and evaluation device in one embodiment;

[0069] Figure 9 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0070] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0071] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0072] In one embodiment, such as Figure 1 As shown, a resource quantification and assessment method is provided. This embodiment illustrates the application of this method to a terminal. It is understood that this method can also be applied to a server, and further to a system including both a terminal and a server, and is implemented through interaction between the terminal and the server. In this embodiment, the method includes the following steps:

[0073] Step 102: Obtain the metadata information and preset transaction indicator information of the system to be tested.

[0074] In this embodiment, the system to be tested can be a business system or a transaction system, etc., and this embodiment is not limited thereto. The metadata information of the business system or transaction system can be data structure information, database information, or network data information, etc. For example, in the data structure information, different data types and objects occupy different amounts of memory; business order objects, user objects, etc., occupy different amounts of memory, which can be used as a basis for memory quantification. Database information can be connection pool memory, memory occupied by database tables or fields, etc. Network data information can be the frequency and rate of data transmission, etc. Preset transaction quality indicators can be transaction concurrency, average transaction processing time, and transaction memory overhead, etc.

[0075] For each system under test that requires resource quantification assessment, the terminal can use static code analysis tools to analyze the code of the business system or transaction system (the system under test), identify the data types and object definitions involved in the system under test, and further identify the memory usage of different data types and objects according to the pre-set memory allocation rules corresponding to the programming language. Alternatively, the terminal can use memory analysis tools to analyze the running status of the system under test in advance. By monitoring memory changes during object creation and destruction in real time during the operation of the system under test, the number of different types of objects and the memory usage of each object can be statistically obtained.

[0076] Regarding database information, the terminal can monitor the memory usage status of the database connection pool using database management tools, thereby obtaining the connection pool memory from the database information. Simultaneously, the terminal can also obtain the memory space occupied by database tables and fields based on database query commands.

[0077] Regarding network data information, the terminal can use network monitoring tools to monitor the network data transmission frequency and rate of the system under test in real time, thereby obtaining network data information during the operation of the system under test. Alternatively, the terminal can also use log analysis tools to analyze the log records of the system under test to obtain network data information. The log records can include network data information such as the time of sending and receiving network data, and the amount of network data transmitted.

[0078] For the preset transaction metrics, the terminal records the number of concurrent transactions based on the application monitoring tool of the system under test, or the terminal analyzes the log records of the system under test based on the log analysis tool to determine the transaction concurrency at different times within the preset time period, the average transaction processing time within the preset time period, and the transaction memory overhead, etc.

[0079] Step 104: Quantify the system resource requirements of the system to be tested based on the preset resource quantification strategy, preset transaction indicator information and metadata information to obtain the target total memory result.

[0080] The target total memory result includes data memory result, business concurrent memory result, and safety buffer memory result.

[0081] In this embodiment, since different systems under test may be applied to different business processing scenarios, the test resources required for testing vary. Specifically, different systems under test handle different types of business. For example, business systems corresponding to basic business operations have a higher transaction concurrency, while product-related business systems may have a lower transaction concurrency. The complexity of the processing flow involved in the business functions also varies in different business systems. For example, a savings system includes account opening, deposits, withdrawals, and inquiries, which have relatively low processing complexity. However, a credit business system, such as loan application, approval, and disbursement, has a more complex processing flow because it needs to connect with other business systems to obtain credit information and customer qualifications. Furthermore, the database table design and data structure design of different systems under test are also different. Therefore, even business systems that process the same business may have different total memory usage. Thus, different systems under test need to be analyzed independently to determine the most suitable target system resources.

[0082] For different systems under test, the terminal performs personalized analysis and calculations based on preset resource quantification strategies, preset transaction indicator information, and metadata information. This serves as the data basis for determining the target system resources suitable for different systems under test, achieving data-driven test resource allocation. Specifically, in the analysis and processing of resources required by the system under test, the terminal uses data memory results, business concurrency memory results, and safety buffer memory results as target dimensions for memory analysis. Data memory results represent the memory overhead of element data such as object headers and indexes, used to quantify the most basic memory requirements supporting the operation of the system under test. Business concurrency memory results represent the memory resources consumed by the system under test to handle concurrent business operations from multiple users. Safety buffer resources are memory resources reserved for the system under test to ensure the stability of system operation under special circumstances.

[0083] Data memory results quantify the memory overhead of the data itself in the system under test, serving as the foundation for the system's operation. Business concurrency memory results address the memory requirements of the system under test in actual business scenarios, reflecting its performance and concurrent processing capabilities. Safety buffer memory results, from a stability perspective, ensure the system under test has the additional reserved resources necessary to operate normally under various risks. Furthermore, by comprehensively analyzing these three dimensions—data memory results, business concurrency memory results, and safety buffer memory results—the accuracy and comprehensiveness of the quantitative analysis of memory usage in the system under test can be improved, providing more accurate data for the allocation of test resources.

[0084] Step 106: Determine the target system resources based on the data memory results, business concurrency memory results, and security buffer memory results, and allocate resources to the system under test according to the target system resources.

[0085] In this embodiment, the terminal uses the data memory result, the service concurrency memory result, and the security buffer memory result as the basis for requesting test resources, and allocates resources to the system under test based on the target system resources. Optionally, after the system under test obtains the target system resources, it performs performance testing (non-functional testing) with the support of the target system resources, and finally obtains the performance test results.

[0086] Specifically, the terminal can use preset load testing tools to simulate real business scenarios for performance testing. These preset tools can be JMeter (a testing tool) or LoadRunner (a performance testing tool). The terminal simulates the maximum peak TPS (Transactions Per Second) using these tools, taking a value greater than 100% of the peak TPS in the real business scenario as the maximum peak TPS. For example, the terminal can simulate the system under test running at 110% of its peak TPS for 4 hours or more using JMeter or LoadRunner. During the system's operation, the frequency of GC (Garbage Collection) and / or the frequency of OOM (Out of Memory) errors are monitored, along with response time, resource utilization, system availability, timeout configuration effectiveness, and the success rate of handling abnormal requests, as performance test results. By allocating test resources individually for each system under test, insufficient resource allocation to the target system can be avoided. If the target system has insufficient resources, Full GC or OOM crashes will frequently occur during performance testing, leading to interruptions and reduced efficiency.

[0087] In an optional embodiment, after completing stress testing using JMeter or LoadRunner, the terminal can further test its fault recovery mechanism and resource configuration. Specifically, based on the baseline stress, the terminal can inject a 200% traffic surge fault and check the CPU or memory auto-scaling thresholds to verify the system's resilience under high load impact, fault recovery mechanism, and the rationality of resource configuration. Applying stress through this traffic injection test step can expose potential problems in the system under test, thereby ensuring the system's resilience in handling sudden traffic spikes. Simultaneously, the data collected during the test can further support system capacity planning and automated operation and maintenance, serving as a basis for optimizing the system's resource configuration, thus ensuring the system operates stably and efficiently under various complex scenarios.

[0088] The aforementioned resource quantification and assessment method, by pre-setting a resource quantification strategy, quantifies the system resource requirements of the system under test according to the dimensions of data memory results, business concurrency memory results, and safety buffer memory results. This improves the accuracy of resource requirement quantification, ensuring that the target system resources match the resource requirements of the system under test. Furthermore, allocating resources to the system under test based on the target system resources determined by the data memory results, business concurrency memory results, and safety buffer memory results improves the accuracy of resource allocation.

[0089] In an exemplary embodiment, the metadata information includes database table metadata information. The calculation of the target total memory result can be quantified using dimensions such as data memory result, business concurrency memory result, and safety buffer memory result. Figure 2 As shown, step 104 includes steps 202 to 206. Wherein:

[0090] Step 202: Calculate the data memory result based on the database table metadata information and the preset expansion coefficient.

[0091] In this embodiment, the terminal collects database table metadata information such as the number of database tables, average field length, and index redundancy rate. It then parses the database table complexity characteristics of entity objects using this metadata and determines a preset inflation coefficient based on these characteristics. Specifically, the database table complexity characteristics can be determined by complexity level or database table type. The terminal can determine the complexity level of the database table structure by comparing the object nesting depth with a preset threshold, or by determining whether the database table structure is a wide or narrow table based on the number of indexes. Finally, it determines the preset inflation coefficient corresponding to the database table metadata information of the current system under test based on the correspondence between the complexity level or database table structure type and the preset inflation coefficient. For example, the preset expansion coefficient can be 1.5 or 2.5, representing the preset expansion coefficients corresponding to the metadata information of simple and complex table structures, respectively. Furthermore, if the terminal determines that the nesting depth of objects in the table structure is greater than the preset threshold, it indicates that the complexity level of the table structure is high, and the preset expansion coefficient is determined to be 2.5; or, if the terminal determines that the number of indexes in the table structure is less than the preset threshold, it indicates that the table structure type is a narrow table, that is, the complexity of the current table structure is low, and the preset expansion coefficient is determined to be 1.5.

[0092] After determining the preset expansion coefficient, the terminal supplements the basic memory overhead required for the database table metadata according to the preset expansion coefficient, and uses the sum of the additional memory overhead and the basic memory overhead as the data memory result.

[0093] Step 204: Calculate the business concurrent memory result based on the preset transaction indicator information.

[0094] In this embodiment of the application, the preset transaction indicator information includes peak TPS. Peak TPS can be determined by historical data and annual growth coefficient. Historical data can be historical business data of the business system to which the current system under test belongs. Annual growth coefficient can be determined based on the growth value of historical business data each year. Alternatively, the terminal can pre-store the annual data volume compound growth rate generated based on financial and business forecasts. Therefore, the terminal can predict the current peak TPS through annual growth coefficient and historical data.

[0095] The preset transaction metrics also include average transaction processing time and single-transaction memory overhead. The terminal calculates the business concurrency memory result based on the peak TPS, average transaction processing time, and single-transaction memory overhead in the preset transaction metric information. At this time, the target total memory result is determined based on the business concurrency memory result obtained from the peak TPS. This ensures that the system under test can operate normally under maximum business concurrency, and performance indicators such as response time and resource utilization can be evaluated under normal operating conditions.

[0096] Step 206: Analyze and calculate the data memory result and the business concurrency memory result according to the preset buffer threshold, and determine the safe buffer memory result.

[0097] In this embodiment, the preset buffer threshold is a pre-set proportion of buffer memory. This proportion can be a measurement indicator pre-set based on business needs and security standards. The preset buffer threshold represents the proportion of memory resources that the system under test needs to reserve to cope with various uncertainties and emergencies.

[0098] The terminal determines the memory resources required for the normal operation of the system under test based on the data memory results and the business concurrency memory results. Then, it multiplies these required memory resources by a preset buffer threshold to obtain the safety buffer memory result that needs to be reserved. This safety buffer memory result is used to handle traffic surges and the memory space required for garbage collection. Optionally, if the data memory result and the business concurrency memory result continue to rise with business growth, the terminal needs to adjust the preset buffer threshold accordingly to ensure that the system under test always has sufficient safety buffer.

[0099] In this embodiment, the data memory result is calculated using database table metadata information and a preset expansion coefficient. This fully considers the impact of database table complexity on memory, accurately obtaining the data memory required for the database tables in the system under test. The business concurrency memory result is calculated based on preset transaction indicator information. Combining historical data, annual growth coefficient, average transaction processing time, and single transaction memory overhead, this ensures the system under test operates normally under maximum business concurrency and allows for effective performance evaluation. Finally, the data memory result and business concurrency memory result are analyzed and calculated based on a preset buffer threshold to determine the safe buffer memory result. This reserves memory space for the system under test to cope with traffic surges and garbage collection. The preset buffer threshold can be adjusted according to business growth to ensure the system always has sufficient safe buffer, thereby improving the accuracy of the test resource analysis for the system under test and, consequently, the accuracy of the target system's resource requirements relative to the system resource requirements of the system under test.

[0100] In one exemplary embodiment, the database table metadata information includes the number of database tables, the average number of fields per table, and the average field length; such as Figure 3 As shown, step 202 includes steps 302 to 304. Wherein:

[0101] Step 302: Determine the initial data memory result based on the number of database tables, the average number of fields per table, and the average field length.

[0102] In this embodiment, during the operation of the system under test, the system's runtime memory needs to temporarily store and process data for the database tables. Specifically, the terminal can analyze the memory usage required for database table operation using the number of tables, the average number of fields per table, and the average field length. The number of tables represents the number of data sets that the system under test needs to process simultaneously during operation; the average number of fields per table represents the complexity of the data structure of each table, i.e., the more fields, the larger the amount of data that needs to be processed and stored during runtime; the average field length represents the temporary storage space occupied by each field during operation. The terminal performs a preliminary quantitative calculation of the basic runtime memory required for the system under test using the number of tables, the average number of fields per table, and the average field length to obtain the initial data memory result.

[0103] Specifically, the terminal can determine the initial data memory result by multiplying the number of database tables, the average number of fields per table, and the average field length.

[0104] Step 304: Correct the initial data memory result according to the preset expansion coefficient to obtain the data memory result.

[0105] In this embodiment of the application, during the actual operation of the database, in addition to the basic amount of running memory required for basic data processing determined based on the database table metadata information, there may also be other traffic surges or garbage collection mechanisms, which also require a certain amount of running memory and affect the use of running memory. For example, the database may need to create temporary indexes for query optimization during runtime, and temporary indexes will occupy a certain amount of running memory; cache management, concurrency control and other operations during data operation will also consume additional running memory.

[0106] Therefore, the terminal allocates the additional runtime memory overhead to the data memory result through a preset inflation coefficient. This is used to correct the initial runtime data memory result, thereby obtaining a runtime data memory result that meets the resource requirements of the data to be tested. Specifically, the data memory result is obtained by multiplying the number of database tables, the average number of fields per table, the average field length, and the preset inflation coefficient.

[0107] In this embodiment, the basic running memory is calculated by the number of database tables, the average number of fields in a single table, and the average field length. By correcting with a preset expansion coefficient, the running memory required by the system under test can be determined more accurately. This provides more accurate data for the allocation of running memory resources for the system under test, improves the accuracy of resource allocation, and also prevents resource waste caused by over-allocation of test resources.

[0108] In an exemplary embodiment, the preset transaction metrics information includes peak transaction concurrency, average transaction processing time, and single transaction memory overhead. Step 204 includes step 2041. Wherein:

[0109] Step 2041: Quantitatively calculate the concurrent memory status of the system under test based on the peak transaction concurrency, average transaction processing time, and single transaction memory overhead to obtain the concurrent business memory results.

[0110] In this embodiment, the terminal uses peak transaction concurrency, average transaction processing time, and single transaction memory overhead as the main dimensions of business concurrency memory analysis, thereby evaluating the test resources required for high-concurrency scenarios of the system under test.

[0111] In high-concurrency business scenarios, peak transaction concurrency represents the maximum number of concurrent transactions the system under test needs to handle. Therefore, as long as the system under test can run normally under peak transaction concurrency, the terminal can perform normal performance testing on the system under test, avoiding test interruptions due to insufficient test resources, improving the efficiency of performance testing, enabling the system under test to perform feasible testing under normal operating conditions, and also improving the accuracy of performance testing. Average transaction processing time represents the average time spent by each transaction from start to finish, reflecting the complexity of the business processing performed by the system under test, and thus quantifying the complexity of business processing, serving as one of the indicators for quantifying concurrent business memory. Single transaction memory overhead is the amount of memory required during the business processing of a single transaction, further quantifying the memory requirements of transaction processing.

[0112] Therefore, the terminal quantifies the concurrent memory status of the system under test based on the peak transaction concurrency, average transaction processing time, and single transaction memory overhead. The product of these three factors is taken as the business concurrent memory result. For example, if the peak transaction concurrency (TPS) is 100, the average transaction processing time (transaction duration) is 0.1s, and the single transaction memory overhead is 2MB, then the concurrent business memory result is 100 × 0.1 × 2 = 20MB.

[0113] In a specific embodiment, the target total memory result is calculated as shown in the following formula (1):

[0114] (1)

[0115] In this embodiment, the peak transaction concurrency, average transaction processing time, and single transaction memory overhead are quantitatively calculated to assess the concurrent memory status of the system under test. This allows for a more comprehensive quantification of the test resources required by the system and improves the accuracy of test resource allocation.

[0116] In one exemplary embodiment, the target system resources also include the target number of processor cores and the target storage space; such as Figure 4 As shown, step 106 includes steps 402 to 406. Wherein:

[0117] Step 402: Obtain incremental data information and determine the total amount of data to be stored based on the incremental data information.

[0118] In this embodiment, incremental data information refers to data added or changed in the database within a certain time range. The test resources allocated to the system under test also include the number of processor cores and storage space. Regarding storage space, the terminal uses the annual data increment as the quantitative basis for incremental data and data redundancy. First, the terminal determines the total amount of data to be stored within a certain future timeframe. This total amount of data storage can be determined based on the annual data increment. For example, the terminal obtains the data increment based on the business system and adds the annual data increment to the previous year's total data storage to obtain the total amount of data storage within a certain future timeframe.

[0119] Step 404: Determine the target number of processor cores based on preset transaction indicator information, and determine the target storage space based on the total amount of data storage.

[0120] In this embodiment, since the system cannot operate at full load for a long time, in order to ensure the stability and reliability of the system, the preset transaction indicator information also includes a utilization threshold. By combining the utilization threshold with the peak transaction concurrency and the average transaction processing time, the number of processor cores is quantified. For the number of processor cores, the terminal determines the target number of processor cores through the preset transaction indicator information. The calculation of the target number of processor cores (CPU cores) is shown in the following formula (1):

[0121] (2)

[0122] Here, peak TPS refers to the peak transaction concurrency, and single-transaction CPU time is the average transaction processing time. The utilization threshold can be pre-set based on the utilization requirements of the system under test; for example, different banks' business systems have different utilization thresholds. Also, if the target number of processor cores is not an integer, it needs to be rounded up. For example, if a system's peak TPS is 1000, single-transaction CPU time is 50ms, and the utilization threshold is 70%, then the calculated number of CPU cores is 71.4. After rounding up, the target number of processor cores is 72.

[0123] The target storage space is calculated based on the total amount of data stored and the redundancy of the data. Specifically, since the data needs to be backed up and maintained, the terminal needs to reserve a certain amount of storage space for the system under test. For example, the index redundancy rate and log redundancy rate represent the proportion of extra storage space occupied by the index and log, and thus the capacity of the index and log needs to be supplemented. The calculation of the target storage space is shown in the following formula (3):

[0124] (3)

[0125] The total amount of data storage can be determined based on the same principle as in step 402. The calculation process for the total amount of data storage will not be described again in this embodiment.

[0126] Step 406: Determine the target system resources based on the data memory results, business concurrency memory results, security buffer memory results, target processor core count, and target storage space.

[0127] In this embodiment, the data memory result reflects the memory size required by the database in the system under test for storing and processing data; the business concurrency memory result reflects the memory requirements of the system under test under high-concurrency business scenarios; and the safety buffer memory result reserves memory space to address the uncertainty of sudden traffic surges. Furthermore, by using the data memory result, business concurrency memory result, and safety buffer memory result as dimensions for memory quantification, the terminal can more comprehensively quantify the memory requirements of the system under test, serving as the target total memory result.

[0128] The terminal quantifies test resources based on the target total memory, target number of processor cores, and target storage space. This allows for a comprehensive assessment of the resources required by the system under test during the testing process, thereby determining reasonable target system resources and ensuring that the test accurately reflects the system's performance and stability.

[0129] The terminal integrates the data memory results, business concurrency memory results, safety buffer memory results, target processor core count, and target storage space. Based on this data, it determines the required server configuration, memory size, storage capacity, and other resource parameters for the test environment. For example, if the data memory result is 500GB, the business concurrency memory result is 300GB, the safety buffer memory result is 200GB, the target processor core count is 100, and the target storage space is 500TB, then the terminal can plan to use a server with the corresponding memory and storage capacity, equipped with 100 processor cores, in the test environment to meet the system resource requirements for the normal operation of the system under test.

[0130] In this embodiment, the resources required by the system under test are quantitatively analyzed by data memory results, business concurrency memory results, security buffer memory results, target processor core count, and target storage space. This enables test resource analysis for different systems under test. At the same time, metadata information and preset transaction indicator information are used as quantitative indicators for test resources, avoiding the subjectivity of manually determining test resources, improving the accuracy of test resources, and thus improving the accuracy of resource allocation for the system under test.

[0131] In one exemplary embodiment, such as Figure 5 As shown, step 106 includes steps 502 to 504. Wherein:

[0132] Step 502: Determine the correction coefficient corresponding to the system resource requirements based on the system type of the system to be tested.

[0133] In this embodiment, the system types of the system under test include IO (Input / Output) intensive applications and high-availability applications. For example, IO intensive applications require more disk IO resources and thread waiting compensation; while high-availability applications require additional redundant resources to ensure the operational stability of the system under test. Therefore, different system types correspond to different correction coefficients. To ensure that the target resources are more suitable for the resource requirements of the system under test, the terminal pre-sets correction coefficients corresponding to each system type. Then, after the terminal performs quantitative analysis on the system under test and obtains the target system resources, the terminal first identifies the system type of the system under test according to the pre-set system type identifier, and then determines the correction coefficient corresponding to the current system resource requirements based on the system type of the system under test.

[0134] Among them, the correction factor for IO-intensive applications can be a compensation factor for thread waiting, which is 1.2; the correction factor for high-availability applications can be the amount of redundant resources added, which is 30%.

[0135] Step 504: Correct the target system resources according to the correction coefficient, and allocate resources according to the corrected target system resources.

[0136] In this embodiment, after determining the correction coefficient based on the system type of the system under test, the terminal determines the indicators to be corrected based on the correction coefficient, and then corrects the indicators according to the correction coefficient. For example, for I / O-intensive applications, the terminal compensates the number of CPU cores determined in the target system resources by 1.2 times, and uses the compensated CPU cores as the target system resources; for high-availability applications, the terminal adds a 30% correction to each item of the target system resources. Finally, the terminal allocates resources according to the corrected target system resources, so that the system under test runs according to the target system resources. For example, after the terminal allocates resources to the system under test according to the corrected target system resources, the system under test can run and perform performance tests under the target system resources, thereby obtaining the performance test results of the system under test. These performance test results can reflect the quantitative accuracy of the target system resources.

[0137] In this embodiment, the target system resources are further modified according to the system type of the system under test, and the test is carried out according to the modified target test system. This can further improve the flexibility of quantifying and allocating test resources for different systems under test, improve the compatibility between the target system resources and the system under test, and thus improve the accuracy of resource allocation for the system under test.

[0138] In one exemplary embodiment, such as Figure 6 As shown, after step 106, the method further includes steps 602 to 604. Wherein:

[0139] Step 602: Verify the preset transaction indicator information, the preset expansion coefficient and the preset buffer threshold in the preset resource quantification strategy based on the performance test results, and obtain the verification results.

[0140] In this embodiment, the performance test results can be the response time, resource utilization (including CPU utilization, memory usage, and disk I / O) of the system under test during the performance test, as well as the effectiveness of timeout configuration and the success rate of handling abnormal requests during the performance test. The terminal can verify the preset inflation coefficient and preset cache threshold by the degree of deviation between the performance test results and the preset standard values. If the deviation is greater than 15% of the standard value, the verification result is determined to be a verification failure; if the deviation is less than or equal to 15%, the verification result is determined to be a verification pass, indicating that the current preset inflation coefficient and preset buffer threshold are highly compatible with the current system under test.

[0141] Step 604: If the verification result is a verification failure, adjust one or more of the preset transaction indicator information, preset expansion coefficient and preset buffer threshold according to the verification result, and perform performance testing based on the adjusted preset transaction indicator information, preset expansion coefficient and preset buffer threshold to obtain new performance test results.

[0142] In this embodiment, when the verification result is a failure, it indicates that the settings of the preset transaction indicator information, preset expansion coefficient, and preset buffer threshold are incompatible with the business processing requirements of the system under test. To ensure the system under test can run stably and efficiently under different business scenarios to meet testing requirements, the preset expansion coefficient and preset buffer threshold need to be adjusted based on the verification result. Performance testing is then conducted based on the adjusted preset transaction indicator information, preset expansion coefficient, and preset buffer threshold to obtain new performance test results. For example, if the system's memory usage exceeds the preset buffer threshold under high concurrency, the terminal triggers an operation to increase the preset buffer threshold; or, if the performance test results indicate that the transaction processing capability of the system under test is insufficient, the terminal adjusts the preset transaction indicator information. After adjustment, the terminal rebuilds the test environment based on the adjusted preset transaction indicator information, preset expansion coefficient, and preset buffer threshold, and performs performance testing on the system under test again to obtain new performance test results. Then, the terminal verifies the new performance test results again. If problems still exist, the adjustment and testing process is repeated until the verification result meets the requirements.

[0143] In this embodiment, by adjusting the preset transaction indicator information, preset expansion coefficient, and preset buffer threshold for failed verification results, the test resources of the system under test can be adjusted in a timely manner, ensuring that the test resources match the business requirements and improving the accuracy of subsequent resource allocation based on the preset transaction indicator information, preset expansion coefficient, and preset buffer threshold.

[0144] In one exemplary embodiment, an example of a resource quantification assessment method is provided, which is applied to a terminal, such as... Figure 7 As shown, it includes:

[0145] Step 701: Extract metadata information in a structured manner.

[0146] Step 702: Quantify the transaction indicators to obtain preset transaction indicator information.

[0147] Step 703: Generate the compound annual growth rate of data volume over N years based on financial and business forecasts, as a growth model.

[0148] Step 704: Calculate the data memory result, business concurrency memory result, security buffer memory result, target processor core count, and target storage space to determine the target system resources.

[0149] Step 705: Correct the target system resources according to the dynamic correction mechanism.

[0150] Step 706: Perform a baseline pressure test.

[0151] Step 707: Verify the preset expansion coefficient and preset buffer threshold of the preset transaction indicator information based on the benchmark stress test results, and obtain the verification results.

[0152] Step 708: Generate a deviation analysis report based on the verification results, which serves as part of the performance test results.

[0153] Step 709: Send the deviation analysis report to each department and instruct each department to adjust the cross-departmental decision-making target system resources.

[0154] Step 710: Summarize the testing of the system to be tested according to the preset specifications to obtain the specification output.

[0155] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0156] Based on the same inventive concept, this application also provides a resource quantification assessment apparatus for implementing the resource quantification assessment method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more resource quantification assessment apparatus embodiments provided below can be found in the limitations of the resource quantification assessment method described above, and will not be repeated here.

[0157] In one exemplary embodiment, such as Figure 8 As shown, a resource quantification and evaluation device 800 is provided, including: an acquisition module 801, a calculation module 802, and an allocation module 803, wherein:

[0158] The acquisition module 801 is used to acquire metadata information and preset transaction indicator information of the system under test.

[0159] The calculation module 802 is used to perform quantitative calculations on the system resource requirements of the system under test based on the preset resource quantification strategy, preset transaction indicator information and metadata information, to obtain the target total memory result; the target total memory result includes data memory result, business concurrency memory result and safety buffer memory result.

[0160] The allocation module 803 is used to determine the target system resources based on the data memory results, business concurrency memory results, and safety buffer memory results, and to allocate resources to the system under test according to the target system resources.

[0161] In one embodiment, the metadata information includes database table metadata information; the calculation module 802 is specifically used to calculate the data memory result based on the database table metadata information and the preset expansion coefficient.

[0162] The business concurrency memory result is obtained by calculating based on preset transaction indicator information;

[0163] The data memory results and business concurrent memory results are analyzed and calculated based on the preset buffer threshold to determine the safe buffer memory result.

[0164] In one embodiment, the database table metadata information includes the number of database tables, the average number of fields per table, and the average field length; the calculation module 802 is specifically used to determine the initial data memory result based on the number of database tables, the average number of fields per table, and the average field length.

[0165] The initial data memory result is corrected and calculated based on the preset expansion coefficient to obtain the data memory result.

[0166] In one embodiment, the preset transaction indicator information includes peak transaction concurrency, average transaction processing time, and single transaction memory overhead; the calculation module 802 is specifically used to quantify the concurrent memory status of the system under test based on the peak transaction concurrency, average transaction processing time, and single transaction memory overhead to obtain the business concurrent memory result.

[0167] In one embodiment, the target system resources also include the target number of processor cores and the target storage space; the allocation module 803 is specifically used to acquire incremental data information and determine the total amount of data storage based on the incremental data information;

[0168] The target number of processor cores is determined based on preset transaction indicator information, and the target storage space is determined based on the total amount of data stored.

[0169] The target system resources are determined based on the data memory results, business concurrency memory results, safety buffer memory results, the number of target processor cores, and the target storage space.

[0170] In one embodiment, the allocation module 803 is specifically used to determine the correction coefficient corresponding to the system resource requirements based on the system type of the system to be tested;

[0171] The target system resources are adjusted according to the adjustment factor, and the resources are allocated according to the adjusted target system resources.

[0172] In one embodiment, the device 800 further includes;

[0173] The verification module is used to verify the preset transaction indicator information, the preset expansion coefficient and the preset buffer threshold in the preset resource quantification strategy based on the performance test results, and obtain the verification results.

[0174] The adjustment module is used to adjust one or more of the preset transaction indicator information, preset expansion coefficient and preset buffer threshold according to the verification result if the verification result is a failure, and to perform performance testing based on the adjusted preset transaction indicator information, preset expansion coefficient and preset buffer threshold to obtain new performance test results.

[0175] Each module in the aforementioned resource quantification and assessment device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0176] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 9As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When executed by the processor, the computer program implements a resource quantification and evaluation method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0177] Those skilled in the art will understand that Figure 9 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0178] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0179] Obtain metadata and preset transaction metrics information of the system under test;

[0180] Based on the preset resource quantification strategy, preset transaction indicator information, and metadata information, the system resource requirements corresponding to the system under test are quantified and calculated to obtain the target total memory result; the target total memory result includes data memory result, business concurrency memory result, and safety buffer memory result;

[0181] The target system resources are determined based on the data memory results, business concurrency memory results, and safety buffer memory results, and the system to be tested is allocated resources according to the target system resources.

[0182] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0183] The data memory result is obtained by calculating based on the database table metadata information and the preset expansion coefficient;

[0184] The business concurrency memory result is obtained by calculating based on preset transaction indicator information;

[0185] The data memory results and business concurrent memory results are analyzed and calculated based on the preset buffer threshold to determine the safe buffer memory result.

[0186] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0187] The initial data memory result is determined based on the number of database tables, the average number of fields per table, and the average field length.

[0188] The initial data memory result is corrected and calculated based on the preset expansion coefficient to obtain the data memory result.

[0189] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0190] The concurrent memory status of the system under test is quantitatively calculated based on the peak transaction concurrency, average transaction processing time, and single transaction memory overhead to obtain the business concurrent memory results.

[0191] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0192] Obtain incremental data information and determine the total amount of data to be stored based on the incremental data information;

[0193] The target number of processor cores is determined based on preset transaction indicator information, and the target storage space is determined based on the total amount of data stored.

[0194] The target system resources are determined based on the data memory results, business concurrency memory results, safety buffer memory results, the number of target processor cores, and the target storage space.

[0195] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0196] Determine the correction factor corresponding to the system resource requirements based on the system type of the system to be tested;

[0197] The target system resources are adjusted according to the adjustment factor, and the resources are allocated according to the adjusted target system resources.

[0198] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0199] Based on the performance test results, the preset transaction indicator information, the preset expansion coefficient and the preset buffer threshold in the preset resource quantification strategy are verified to obtain the verification results.

[0200] If the verification result is a verification failure, one or more of the preset transaction indicator information, preset expansion coefficient and preset buffer threshold are adjusted according to the verification result, and a performance test is performed based on the adjusted preset transaction indicator information, preset expansion coefficient and preset buffer threshold to obtain a new performance test result.

[0201] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps in the above method embodiments.

[0202] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0203] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0204] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0205] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0206] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for quantitative assessment of resources, characterized in that, The method includes: Obtain metadata and preset transaction metrics information of the system under test; The system resource requirements of the system under test are quantified and calculated based on the preset resource quantification strategy, the preset transaction indicator information, and the metadata information to obtain the target total memory result; the target total memory result includes data memory result, business concurrency memory result, and safety buffer memory result; Based on the data memory results, the business concurrency memory results, and the security buffer memory results, the target system resources are determined, and the system under test is allocated resources according to the target test resources.

2. The method according to claim 1, characterized in that, The metadata information includes database table metadata information; the step of quantifying and calculating the system resource requirements corresponding to the system under test based on the preset resource quantification strategy, the preset transaction indicator information, and the metadata information to obtain the target total memory result includes: The data memory result is obtained by calculating based on the database table metadata information and the preset expansion coefficient; The business concurrency memory result is obtained by calculating based on the preset transaction index information; The data memory result and the business concurrency memory result are analyzed and calculated based on the preset buffer threshold to determine the safe buffer memory result.

3. The method according to claim 2, characterized in that, The database table metadata information includes the number of database tables, the average number of fields per table, and the average field length. The calculation based on the database table metadata information and the preset expansion coefficient to obtain the data memory result includes: The initial data memory result is determined based on the number of database tables, the average number of fields per table, and the average field length. The initial data memory result is corrected and calculated based on a preset expansion coefficient to obtain the data memory result.

4. The method according to claim 2, characterized in that, The preset transaction metrics include peak transaction concurrency, average transaction processing time, and single transaction memory overhead; the calculation of business concurrency memory results based on the preset transaction metrics includes: The concurrent memory status of the system under test is quantitatively calculated based on the peak transaction concurrency, the average transaction processing time, and the single transaction memory overhead to obtain the business concurrent memory result.

5. The method according to claim 1, characterized in that, The target system resources also include the target number of processor cores and the target storage space; determining the target system resources based on the data memory results, the business concurrency memory results, and the security buffer memory results includes: Obtain incremental data information and determine the total amount of data to be stored based on the incremental data information; The target number of processor cores is determined based on the preset transaction indicator information, and the target storage space is determined based on the total amount of data storage. The target system resources are determined based on the data memory results, the business concurrency memory results, the security buffer memory results, the target number of processor cores, and the target storage space.

6. The method according to claim 1, characterized in that, The step of allocating resources to the system under test based on the target system resources includes: Based on the system type of the system to be tested, determine the correction coefficient corresponding to the system resource requirements; The target system resources are corrected according to the correction coefficient, and resources are allocated according to the corrected target system resources.

7. The method according to claim 1, characterized in that, After allocating resources to the system under test according to the target system resources, the method further includes: Based on the performance test results, the preset transaction indicator information, the preset expansion coefficient and the preset buffer threshold in the preset resource quantification strategy are verified to obtain the verification results. If the verification result is a verification failure, one or more of the preset transaction indicator information, the preset expansion coefficient, and the preset buffer threshold are adjusted according to the verification result, and a performance test is performed based on the adjusted preset transaction indicator information, the preset expansion coefficient, and the preset buffer threshold to obtain a new performance test result.

8. A resource quantification and assessment device, characterized in that, The device includes: The acquisition module is used to acquire metadata information and preset transaction indicator information of the system under test. The calculation module is used to quantify the system resource requirements of the system under test according to the preset resource quantification strategy, the preset transaction indicator information and the metadata information, and obtain the target total memory result; the target total memory result includes data memory result, business concurrency memory result and safety buffer memory result; The allocation module is used to determine the target system resources based on the data memory results, the business concurrency memory results, and the security buffer memory results, and to allocate resources to the system under test according to the target system resources.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images