Equipment performance data management method and device, computer equipment and storage medium

Abstract

The invention relates to an equipment performance data management method and device, computer equipment and a storage medium. The method comprises the following steps: determining an equipment driving interface and an architecture specific index according to an equipment architecture type; obtaining platform general indexes, and combining the architecture specific indexes to obtain an index conversion relation table; acquiring original performance data of the equipment through the equipment driving interface; processing the original performance data of the equipment into abstract performance data through a preset driving isolation abstraction layer; and based on the index conversion relation table, analyzing and standardizing the abstract performance data to obtain platform standard performance data, and storing the platform standard performance data into a database. By adopting the method, unified standard data acquisition and management of heterogeneous GPUs can be realized, customer requirements can be quickly responded, the resource utilization rate is improved, and the driving compatibility and stability of the system are improved.

Description

Technical Field

[0001] The present application relates to the technical field of equipment performance data management, and in particular to an equipment performance data management method, device, computer equipment and storage medium. Background Art

[0002] As the demand for artificial intelligence and high-performance computing grows, different manufacturers, such as NVIDIA, AMD, Intel, etc., have launched various types of GPUs with different architectures and performance characteristics, which also put forward higher requirements for their data management and performance monitoring.

[0003] In the prior art, due to the lack of unified standards and universal monitoring data acquisition methods, it is difficult to unify the data management and performance monitoring of heterogeneous GPUs, and targeted adaptation development is required. Not only is the development cycle long, but it is also unable to quickly respond to customer needs, and the GPU will be idle during the adaptation process, resulting in a waste of resources. At the same time, the targeted adaptation development data management system method adopted by the prior art usually uses monitoring scripts to directly rely on the GPU driver interface. When the GPU driver interface is upgraded, it is difficult to achieve timely update response, resulting in driver compatibility issues, which can easily cause the entire data management system to be unavailable, affecting system stability. Summary of the invention

[0004] Based on this, it is necessary to provide a device performance data management method, apparatus, computer equipment and storage medium that can realize unified standard data collection and management of heterogeneous GPUs, quickly respond to customer needs, improve resource utilization, and enhance the system's driver compatibility and stability in response to the above technical problems.

[0005] In one aspect, a method for managing equipment performance data is provided, the method comprising:

[0006] Determine the device driver interface and architecture-specific indicators based on the device architecture type;

[0007] Obtaining platform general indicators and combining them with the architecture specific indicators to obtain an indicator conversion relationship table;

[0008] Obtaining original performance data of the device through the device driver interface;

[0009] Processing the original performance data of the device into abstract performance data through a preset driver isolation abstraction layer;

[0010] Based on the indicator conversion relationship table, the abstract performance data is parsed and standardized to obtain platform standard performance data, and the platform standard performance data is stored in a database.

[0011] In one embodiment, a platform-wide indicator is obtained and combined with the architecture-specific indicator to obtain an indicator conversion relationship table, wherein the platform-wide indicator is obtained by the following method:

[0012] Obtain historical equipment usage records and mark all used equipment;

[0013] According to the previously used equipment, a corresponding equipment architecture is determined, and a previously used architecture indicator is obtained;

[0014] Extracting commonalities from the previously used architecture indicators to obtain basic general indicators;

[0015] Performing characteristic performance index screening and analysis on the extracted previously used architecture index to obtain characteristic performance index;

[0016] The platform general indicators are obtained according to the basic general indicators in combination with the characteristic performance indicators.

[0017] In one embodiment, the platform general indicator is obtained, combined with the architecture specific indicator, to obtain an indicator conversion relationship table, including:

[0018] According to the architecture-specific indicator, a check is performed in the platform-general indicators to determine whether the architecture-specific indicator is an entered indicator;

[0019] In response to a negative result of the judgment, the architecture-specific indicator is subjected to indicator conversion processing to obtain a specific conversion indicator, and the specific conversion indicator is added to the platform-general indicator;

[0020] If the judgment result is yes, the conversion relationship between the architecture-specific indicator and the platform-general indicator is determined, and based on the conversion relationship, the indicator conversion relationship table is constructed.

[0021] In one embodiment, the original performance data of the device is processed into abstract performance data through a preset driver isolation abstraction layer, wherein the driver isolation abstraction layer performs the following steps:

[0022] Receiving the original performance data of the device transmitted by the device driver interface;

[0023] Obtaining the platform general indicators and the indicator conversion relationship table;

[0024] Performing field extraction on the original performance data of the device and the general indicators of the platform respectively to obtain original fields and indicator fields;

[0025] According to the original field, combined with the indicator field, the field status of the original performance data of the device is judged;

[0026] According to the result of the field status judgment, the original performance data of the device is processed to obtain the abstract performance data, and the indicator conversion relationship table is updated.

[0027] In one embodiment, the processing of the original performance data of the device according to the result of the field status judgment to obtain the abstract performance data and updating the indicator conversion relationship table includes:

[0028] In response to the existence of the original field and the platform general indicator not having the corresponding indicator field, the original field is a newly added field, the indicator field is added to the indicator conversion relationship table, and the corresponding conversion relationship is set to no conversion;

[0029] In response to the existence of the indicator field, but the corresponding original field does not exist in the original performance data of the device, the indicator field is a discarded field, and the indicator field is marked as disabled in the indicator conversion relationship table;

[0030] In response to the existence of both the original field and the corresponding indicator field, performing type consistency judgment based on field types of the original field and the corresponding indicator field;

[0031] In response to the field types of the original field and the corresponding indicator field being inconsistent, the original field is subjected to field type conversion, wherein the field type conversion includes at least one of the following: converting a value to a string, or converting a string to a value;

[0032] In response to the field type conversion being successful, the corresponding conversion relationship in the indicator conversion relationship table is updated, otherwise, it is marked as conversion failure;

[0033] In response to the device original performance data completing the field status judgment and the corresponding field type conversion, the device original performance data is uniformly formatted and encapsulated into the abstract performance data.

[0034] In one embodiment, based on the indicator conversion relationship table, the abstract performance data is parsed and standardized to obtain platform standard performance data, including:

[0035] Traverse all fields in the abstract performance data to obtain abstract data fields;

[0036] Based on the name of the abstract data field, searching in the indicator conversion relationship table to determine the corresponding conversion rule;

[0037] Based on the platform general indicator, the field type of the abstract data field is verified, and in response to the verification result being inconsistent, the type of the abstract data field is converted according to the conversion rule, otherwise, no conversion is required;

[0038] According to the conversion rules, the abstract performance data is subjected to data standardization processing and storage adaptability processing respectively to obtain platform standard performance data, wherein the selection of the storage adaptability processing is based on the type of the database.

[0039] In one embodiment, after storing the platform standard performance data in a database, the method includes:

[0040] Based on the general indicators, the standard performance data of the platform is obtained from the database for visual output to obtain a basic dashboard;

[0041] Obtain the business type specified by the user, perform indicator analysis based on the business type, and obtain key performance indicators;

[0042] According to the key performance indicators, the corresponding common indicators in the basic dashboard are screened to generate a recommended configuration dashboard.

[0043] In another aspect, a device performance data management apparatus is provided, the apparatus comprising:

[0044] A device identification module is used to determine the device driver interface and architecture-specific indicators according to the device architecture type;

[0045] An indicator conversion relationship generation module is used to obtain the platform general indicators and combine them with the architecture specific indicators to obtain an indicator conversion relationship table;

[0046] A drive data acquisition module, used to obtain original performance data of the device through the device drive interface;

[0047] An isolation abstract processing module, used for processing the original performance data of the device into abstract performance data based on a preset driver isolation abstract layer;

[0048] The data parsing and storage module is used to parse and standardize the abstract performance data based on the indicator conversion relationship table, obtain platform standard performance data, and store the platform standard performance data in a database.

[0049] In another aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the following steps are implemented:

[0050] Determine the device driver interface and architecture-specific indicators based on the device architecture type;

[0051] Obtaining platform general indicators and combining them with the architecture specific indicators to obtain an indicator conversion relationship table;

[0052] Obtaining original performance data of the device through the device driver interface;

[0053] Processing the original performance data of the device into abstract performance data through a preset driver isolation abstraction layer;

[0054] Based on the indicator conversion relationship table, the abstract performance data is parsed and standardized to obtain platform standard performance data, and the platform standard performance data is stored in a database.

[0055] In another aspect, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0056] Determine the device driver interface and architecture-specific indicators based on the device architecture type;

[0057] Obtaining platform general indicators and combining them with the architecture specific indicators to obtain an indicator conversion relationship table;

[0058] Obtaining original performance data of the device through the device driver interface;

[0059] Processing the original performance data of the device into abstract performance data through a preset driver isolation abstraction layer;

[0060] Based on the indicator conversion relationship table, the abstract performance data is parsed and standardized to obtain platform standard performance data, and the platform standard performance data is stored in a database.

[0061] The above-mentioned device performance data management method, device, computer equipment and storage medium, by combining architecture-specific indicators with platform-general indicators, construct an indicator conversion relationship table and standardize the device performance data, which helps to solve the problem of standardization of device performance data of different architectures, thereby improving data compatibility and availability, reducing the complexity of data management caused by hardware architecture differences, and avoiding the waste of time and resources caused by targeted adaptation development; at the same time, by presetting the driver isolation abstraction layer, the data acquisition and driver interface can be decoupled, avoiding the strong dependence of data acquisition on the driver interface in traditional technologies, and reducing the risk of interface unavailability due to driver upgrades, thereby affecting the normal acquisition of data and causing system unavailability, thereby improving the stability and reliability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] Figure 1An application environment diagram of a device performance data management method in an embodiment;

[0063] Figure 2 A schematic diagram of a process flow of a device performance data management method in one embodiment;

[0064] Figure 3 is a structural block diagram of a device performance data management apparatus in one embodiment;

[0065] Figure 4 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0066] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0067] The device performance data management method provided in this application can be applied to Figure 1 In the application environment shown. The terminal 102 communicates with the server 104 through the network. The terminal 102 sends a device performance data call request to the server 104. After receiving the device performance data call request, the server obtains the platform standard performance data stored in the database according to the device performance data management method and returns it to the terminal 102. The terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices, and the server 104 can be implemented by an independent server or a server cluster composed of multiple servers.

[0068] In one embodiment, Figure 2 As shown, a device performance data management method is provided, which is applied to Figure 1 The server 104 in the example is used as an example to illustrate, and the following steps are included:

[0069] Step 201, determining the device driver interface and architecture specific indicators according to the device architecture type.

[0070] Among them, the device architecture type refers to the manufacturer or supplier of the device (such as NVIDIA, AMD, Intel, etc.). These architectures provide different types of hardware devices, such as GPU, CPU, memory, etc.; the device driver interface is the interface between the hardware and the operating system or management software, which is responsible for the management, monitoring and control of the device. The system or software can obtain device information through the driver interface; architecture-specific indicators are defined by the device architecture and are specific data or parameters used to measure and monitor device performance. Different architectures may use different naming, data formats or metrics.

[0071] Step 202, obtain the platform general indicators, combine them with the architecture specific indicators, and obtain an indicator conversion relationship table.

[0072] Specifically, historical equipment usage records are obtained to obtain previously used architecture indicators; basic general indicators are obtained based on previously used architecture indicators; basic general indicators are further supplemented based on previously used architecture indicators and architecture-specific indicators to obtain platform general indicators; based on platform general indicators, the conversion relationship between architecture-specific indicators and platform general indicators is determined to construct an indicator conversion relationship table.

[0073] Step 203: Obtain original performance data of the device through the device driver interface.

[0074] The raw device performance data refers to the unprocessed performance data collected directly from the hardware through the device driver interface. It is usually the original number related to the operating status of the device hardware, and the data format is architecture-specific.

[0075] Specifically, a data acquisition request is sent to the hardware device through the device driver interface to obtain the real-time performance data of the device, that is, the original performance data of the device.

[0076] Step 204: Processing the original performance data of the device into abstract performance data through a preset driver isolation abstraction layer.

[0077] Specifically, the original performance data of the device transmitted by the device driver interface is received through the driver isolation abstraction layer; the platform general indicators and the indicator conversion relationship table are obtained; according to the platform general indicators, the field status of the fields in the original performance data of the device is judged; according to the result of the field status judgment, the original performance data of the device is processed to obtain abstract performance data, and the indicator conversion relationship table is updated.

[0078] Step 205, based on the indicator conversion relationship table, the abstract performance data is parsed and standardized to obtain platform standard performance data, and the platform standard performance data is stored in the database.

[0079] Specifically, based on the platform's common indicators, the field type of the abstract data field is verified. If the verification result is inconsistent, the abstract data field is converted based on the indicator conversion relationship table. Otherwise, no conversion is required. The abstract performance data with consistent verification results is subjected to data standardization and warehousing adaptability processing to obtain platform standard performance data.

[0080] In the above-mentioned device performance data management method, by combining architecture-specific indicators with platform-general indicators, constructing an indicator conversion relationship table, and standardizing device performance data, it is helpful to solve the problem of standardization of device performance data of different architectures, thereby improving data compatibility and availability, reducing the complexity of data management caused by hardware architecture differences, and avoiding the waste of time and resources caused by targeted adaptation development; at the same time, by presetting the driver isolation abstraction layer, the data acquisition and driver interface can be decoupled, avoiding the strong dependence of data acquisition on the driver interface in traditional technologies, and reducing the risk of interface unavailability due to driver upgrades, thereby affecting the normal acquisition of data and causing system unavailability, thereby improving the stability and reliability of the system.

[0081] In one embodiment, the platform general indicators are obtained and combined with the architecture specific indicators to obtain an indicator conversion relationship table, wherein the platform general indicators are obtained by the following method:

[0082] Obtain historical equipment usage records and mark all used equipment;

[0083] According to the previously used equipment, determine the corresponding equipment architecture and obtain the previously used architecture index;

[0084] Extract commonalities from previously used architecture indicators to obtain basic general indicators;

[0085] Screening and analyzing the extracted used architecture indicators for characteristic performance indicators to obtain characteristic performance indicators;

[0086] Based on the basic general indicators and combined with the characteristic performance indicators, the platform general indicators are obtained.

[0087] Specifically, this embodiment obtains historical equipment usage records, marks all used equipment, and extracts common indicators based on architecture indicators, so that the platform performance data management system has higher versatility and adaptability, helps to build a high-availability platform common indicator, thereby providing a basis for subsequent data standardization and performance analysis, reducing dependence on a single architecture device, and improving the scalability of the system.

[0088] It is worth noting that the commonality extraction of architecture indicators was carried out to obtain basic general indicators, which specifically includes the following steps:

[0089] Collect and record historical device usage, including device model, architecture information, and usage metrics data.

[0090] According to the device information in the historical records, the device architectures that have been used are determined, and the indicators of the used architectures are extracted from the indicator data provided by each device architecture.

[0091] By comparing the indicator data provided by different architectures, we can find out the common indicators between them, which are the basic common indicators.

[0092] Determine the definition and data format of basic common indicators to ensure that they can be uniformly identified and processed by the system.

[0093] It is worth noting that the basic general indicators are obtained through commonality extraction, which can find the common standards between different device architectures and efficiently determine the most critical indicators of the device; however, due to the differences in some indicators between different device architectures, key indicators may be omitted, so it is necessary to obtain characteristic performance indicators to supplement the basic general indicators, so as to obtain high-availability platform general indicators, wherein the characteristic performance indicators are obtained specifically including the following steps:

[0094] Obtaining screening criteria, wherein the screening criteria are obtained based on at least one of the following dimensions: relevance, importance, and availability;

[0095] Obtain the used architecture indicators after extracting the basic common indicators, and record them as the remaining architecture indicators;

[0096] According to the basic general indicators, the remaining architecture indicators are analyzed in turn to obtain the correlation scores between the remaining architecture indicators and the basic general indicators;

[0097] Obtain historical equipment performance data, combine it with historical equipment usage records, evaluate the impact of remaining architecture indicators on equipment performance, and perform importance scoring;

[0098] According to the difficulty of data collection corresponding to the remaining architecture indicators, the reliability score is obtained. If the data can be collected directly, the reliability score is 1. The reliability score decreases by 10-30% for each additional calculation required to obtain the data corresponding to the indicator.

[0099] According to the remaining architecture indicators, the corresponding relevance score, importance score and availability score are assigned corresponding preset weights, and weighted calculation is performed to obtain the feature score;

[0100] The remaining architecture indicators whose feature scores are in the top 10-20% and meet the preset threshold are selected as feature performance indicators.

[0101] In one embodiment, the platform general indicators are obtained and combined with the architecture specific indicators to obtain an indicator conversion relationship table, including:

[0102] According to the architecture-specific indicators, check the platform common indicators to determine whether the architecture-specific indicators are entered indicators;

[0103] In response to the judgment result being negative, the architecture-specific indicator is subjected to indicator conversion processing to obtain a specific conversion indicator, and the specific conversion indicator is added to the platform general indicator;

[0104] If the judgment result is yes, the conversion relationship between the architecture-specific indicators and the platform-general indicators is determined, and based on the conversion relationship, an indicator conversion relationship table is constructed.

[0105] Specifically, this embodiment ensures the continuous updating and integrity of the platform's general indicator library by determining whether the architecture-specific indicator is an already entered indicator and performing necessary conversion and supplementary recording. It can improve adaptability to new devices and architecture indicators, reduce resource waste caused by idle equipment, avoid the defects of hard coding or customized development in traditional methods, and enhance the flexibility and long-term applicability of the system.

[0106] In one embodiment, the original performance data of the device is processed into abstract performance data through a preset driver isolation abstraction layer, wherein the driver isolation abstraction layer performs the following steps:

[0107] Receive the original performance data of the device transmitted by the device driver interface;

[0108] Obtain the platform's general indicators and indicator conversion relationship table;

[0109] Extract fields from the original performance data of the device and the common indicators of the platform to obtain original fields and indicator fields;

[0110] According to the original field and the indicator field, the field status of the original performance data of the equipment is judged;

[0111] According to the results of field status judgment, the original performance data of the equipment is processed to obtain abstract performance data, and the indicator conversion relationship table is updated.

[0112] Specifically, this embodiment processes and standardizes the original performance data through the driver isolation abstraction layer, thereby improving the processing efficiency of the performance data and ensuring the compatibility of cross-platform devices; at the same time, through the setting of the driver isolation abstraction layer, the system can maintain the stability of the data processing logic when the device driver changes, and effectively reduce the system instability caused by driver upgrades.

[0113] It is worth noting that the driver isolation abstraction layer communicates with the device driver through the device driver interface and receives the original performance data of the device. Moreover, after the driver isolation abstraction layer processes the original performance data of the device into abstract performance data, it sends the abstract performance data to the monitoring script, and the monitoring script then sends the abstract performance data for subsequent processing.

[0114] Specifically, in the absence of a driver isolation abstraction layer, when a device driver is upgraded or switched to a driver of a different architecture, the monitoring script must be adjusted accordingly to the new driver version or architecture API. The update of the device driver may change the data format, API interface or other behaviors, which means that the monitoring script may need to be modified to adapt to these changes, resulting in increased maintenance and development costs; however, the introduction of a driver isolation abstraction layer can encapsulate driver differences into an intermediary layer for unifying interfaces and data formats and realizing data conversion.

[0115] Specifically, the driver isolation abstraction layer accesses the data of different device drivers by defining a unified standard interface (such as a unified API or data structure). No matter how the driver version or architecture changes, the monitoring script only needs to interact with the driver isolation abstraction layer and does not need to worry about the specific driver implementation. At the same time, the driver isolation abstraction layer converts the data of different drivers so that the monitoring script can obtain data in a unified format no matter which device driver it obtains the data from. It is responsible for processing the mapping of raw data fields, format conversion, and other tasks to ensure that the script does not depend on the implementation details of a specific driver and avoid frequent script modifications. In addition, when processing the original performance data, the driver isolation abstraction layer will also update the indicator conversion relationship table based on the comparison results of the original performance data and the platform's general indicators, so that it can show better adaptability when facing changes in driver interfaces and indicators.

[0116] In one embodiment, according to the result of field status judgment, the original performance data of the device is processed to obtain abstract performance data, and the indicator conversion relationship table is updated, including:

[0117] In response to the existence of the original field, but the corresponding indicator field does not exist for the platform general indicator, the original field is a newly added field, and a new indicator field is added to the indicator conversion relationship table, and the corresponding conversion relationship is set to no conversion;

[0118] In response to the indicator field existing, but the corresponding original field does not exist in the original performance data of the device, the indicator field is a discarded field, and the indicator field is marked as disabled in the indicator conversion relationship table;

[0119] In response to the existence of both the original field and the corresponding indicator field, performing type consistency judgment based on the field types of the original field and the corresponding indicator field;

[0120] In response to the inconsistency between the field types of the original field and the corresponding indicator field, the original field is converted into a field type, wherein the field type conversion includes at least one of the following: converting a value into a string, converting a string into a value;

[0121] In response to a successful conversion of the field type, the corresponding conversion relationship in the indicator conversion relationship table is updated, otherwise, it is marked as a conversion failure;

[0122] In response to the device original performance data completing the field status judgment and the corresponding field type conversion, the device original performance data is uniformly formatted and encapsulated into abstract performance data.

[0123] It is worth noting that in response to the inconsistency between the field types of the original field and the corresponding indicator field, the original field is converted to a field type, wherein the field type conversion includes at least one of the following: converting a value to a string, converting a string to a value, and specifically includes the following steps:

[0124] Get the field type of the original field. The field type of the original field is at least one of the following: value, string;

[0125] In response to the field type of the original field being a numeric value, the conversion is performed directly, the field type after conversion is a string, and the corresponding conversion relationship in the indicator conversion relationship table is updated;

[0126] In response to the character type of the original field being a string, the original field is preferentially converted to a double value; it is worth noting that the conversion of a value to a string generally does not fail, while the conversion of a string to a value may fail. Therefore, in response to the failure of the double value conversion, the corresponding conversion relationship in the indicator capture relationship table is marked as a conversion failure, triggering the conversion failure processing mechanism.

[0127] Specifically, the conversion failure handling mechanism includes:

[0128] Record conversion failure information, including failure timestamp, original performance data, failure field, and failure reason;

[0129] Prompt an alarm notification for conversion failure information, and stop data collection and processing of corresponding original performance data;

[0130] Obtain the preset automatic repair rules, and query whether there is a repair processing method for the corresponding situation in the preset automatic repair rules according to the failure reason of the conversion failure information, wherein the preset automatic repair rules include: writing scripts to automatically clean and format data for specific data format errors;

[0131] In response to the existence of a repair processing method corresponding to the condition, adjusting the original performance data according to the corresponding repair processing method and attempting to reconvert;

[0132] In response to the absence of a corresponding repair processing method or the reconversion failure, the original performance data is rolled back according to the failure timestamp, the original performance data is restored to the state before the failure, and marked as priority processing data;

[0133] The priority data will be processed through manual correction or artificial intelligence analysis until the priority data is successfully converted. Then, the data collection and processing of the corresponding original performance data will be restored, and the corresponding processing method will be recorded in the preset repair rules.

[0134] Specifically, by adopting the above automated processing method, the problems caused by conversion failures can be significantly reduced, and the responsiveness and stability of the system can be improved, thereby more effectively managing and handling abnormal situations in the data conversion process.

[0135] Specifically, this embodiment processes the original performance data of the equipment and updates the indicator conversion relationship table according to the field status judgment, which helps to deal with the problem of inconsistent data formats and ensures the formatting and uniformity of the data, effectively improving the quality and consistency of the data and ensuring that the data can smoothly enter the subsequent standardization and storage links.

[0136] In one embodiment, based on the indicator conversion relationship table, the abstract performance data is parsed and standardized to obtain the platform standard performance data, including:

[0137] Traverse all fields in the abstract performance data to obtain abstract data fields;

[0138] Based on the name of the abstract data field, search in the indicator conversion relationship table to determine the corresponding conversion rule;

[0139] Based on the platform general indicators, the field type of the abstract data field is verified. If the verification result is inconsistent, the type of the abstract data field is converted according to the conversion rule. Otherwise, no conversion is required.

[0140] According to the conversion rules, the abstract performance data is subjected to data standardization processing and storage adaptability processing respectively to obtain the platform standard performance data, wherein the selection of storage adaptability processing is based on the type of database.

[0141] Specifically, in the standardization process of this embodiment, the data fields are type converted and processed according to the indicator conversion relationship table, which improves the compatibility of the data, helps to optimize the data storage and subsequent analysis process, ensures data quality and improves the efficiency of subsequent queries and operations.

[0142] In one embodiment, after storing the platform standard performance data in the database, the method includes:

[0143] Based on common indicators, the platform standard performance data is obtained from the database for visualization output to obtain a basic dashboard;

[0144] Obtain the business type specified by the user, perform indicator analysis based on the business type, and obtain key performance indicators;

[0145] According to the key performance indicators, the corresponding common indicators in the basic dashboard are filtered to generate a recommended configuration dashboard.

[0146] Specifically, in this embodiment, after the platform standard performance data is stored in the database, customized performance analysis and display results can be provided to users through visualization output and key performance indicator analysis of business types, which is conducive to improving the user's efficiency in obtaining performance information in a variety of usage scenarios, and generating recommended configurations based on business needs, thereby improving the user's decision-making efficiency and the practicality of the system.

[0147] It should be understood that although Figure 2 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0148] In one embodiment, Figure 3 As shown, a device performance data management device is provided, including: a device identification module, an indicator conversion relationship generation module, a drive data acquisition module, an isolation abstract processing module and a data analysis and storage module, wherein:

[0149] A device identification module is used to determine the device driver interface and architecture-specific indicators according to the device architecture type;

[0150] The indicator conversion relationship generation module is used to obtain the platform general indicators and combine them with the architecture specific indicators to obtain the indicator conversion relationship table;

[0151] The drive data acquisition module is used to obtain the original performance data of the device through the device driver interface;

[0152] An isolation abstract processing module is used to process the original performance data of the device into abstract performance data based on a preset driver isolation abstract layer;

[0153] The data analysis and storage module is used to analyze and standardize the abstract performance data based on the indicator conversion relationship table, obtain the platform standard performance data, and store the platform standard performance data in the database.

[0154] The indicator conversion relationship generation module is used to obtain historical equipment usage records and mark all previously used equipment; determine the corresponding equipment architecture based on previously used equipment and obtain previously used architecture indicators; extract commonalities from previously used architecture indicators to obtain basic general indicators; screen and analyze characteristic performance indicators of the extracted previously used architecture indicators to obtain characteristic performance indicators; and obtain platform general indicators based on basic general indicators and combined with characteristic performance indicators.

[0155] The indicator conversion relationship generation module is also used to check the platform common indicators according to the architecture-specific indicators to determine whether the architecture-specific indicators are entered indicators; in response to the judgment result being no, the architecture-specific indicators are subjected to indicator conversion processing to obtain specific conversion indicators, and the specific conversion indicators are added to the platform common indicators; if the judgment result is yes, the conversion relationship between the architecture-specific indicators and the platform common indicators is determined, and based on the conversion relationship, an indicator conversion relationship table is constructed.

[0156] The drive data acquisition module is used to send a data acquisition request to the hardware device through the device driver interface to obtain the real-time performance data of the device, that is, the original performance data of the device.

[0157] The isolation abstract processing module is used to obtain the abstract performance data processed by the driver isolation abstract layer, wherein the driver data acquisition module calls the driver abstract isolation layer to perform the following steps: receiving the original performance data of the device transmitted by the device driver interface; obtaining the platform general indicators and the indicator conversion relationship table; performing field extraction on the original performance data of the device and the platform general indicators respectively to obtain the original fields and the indicator fields; judging the field status of the original performance data of the device based on the original fields and in combination with the indicator fields; processing the original performance data of the device based on the result of the field status judgment to obtain the abstract performance data, and updating the indicator conversion relationship table.

[0158] The isolation abstract processing module is also used to call the driver isolation abstract layer to perform the following steps: in response to the existence of the original field, but the corresponding indicator field does not exist in the platform general indicator, the original field is a newly added field, and a new indicator field is added to the indicator conversion relationship table, and the corresponding conversion relationship is set to no conversion; in response to the existence of the indicator field, but the corresponding original field does not exist in the original performance data of the device, the indicator field is a discarded field, and the indicator field is marked as disabled in the indicator conversion relationship table; in response to the existence of both the original field and the corresponding indicator field, a type consistency judgment is performed based on the field types of the original field and the corresponding indicator field; in response to the inconsistency of the field types of the original field and the corresponding indicator field, the original field is converted to a field type, wherein the field type conversion includes at least one of the following: value to string, string to value; in response to a successful field type conversion, the corresponding conversion relationship in the indicator conversion relationship table is updated, otherwise, it is marked as a conversion failure; in response to the completion of the field status judgment and the corresponding field type conversion of the original performance data of the device, the original performance data of the device is uniformly formatted and encapsulated as abstract performance data.

[0159] The data parsing and storage module is used to traverse all fields in the abstract performance data to obtain abstract data fields; based on the name of the abstract data field, search in the indicator conversion relationship table to determine the corresponding conversion rule; based on the platform common indicator, the field type of the abstract data field is verified, and in response to the verification result being inconsistent, the abstract data field is converted according to the conversion rule, otherwise, no conversion is required; according to the conversion rule, the abstract performance data is subjected to data standardization processing and warehousing adaptability processing respectively to obtain platform standard performance data, wherein the selection of warehousing adaptability processing is based on the type of database.

[0160] In one embodiment, the database is connected to a data display module, which is used to obtain platform standard performance data from the database for visual output based on general indicators to obtain a basic dashboard; obtain the business type specified by the user, perform indicator analysis based on the business type, and obtain key performance indicators; based on the key performance indicators, filter the corresponding general indicators in the basic dashboard to generate a recommended configuration dashboard.

[0161] For the specific definition of the device performance data management device, please refer to the definition of the device performance data management method above, which will not be repeated here. Each module in the above-mentioned device performance data management device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0162] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 4 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store device performance data management data. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a device performance data management method is implemented.

[0163] Those skilled in the art will understand that Figure 4 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0164] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:

[0165] Determine the device driver interface and architecture-specific indicators based on the device architecture type;

[0166] Get the platform general indicators, combine them with the architecture specific indicators, and get the indicator conversion relationship table;

[0167] Obtain the original performance data of the device through the device driver interface;

[0168] Through the preset driver isolation abstraction layer, the original performance data of the device is processed into abstract performance data;

[0169] Based on the indicator conversion relationship table, the abstract performance data is parsed and standardized to obtain the platform standard performance data, and the platform standard performance data is stored in the database.

[0170] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0171] Obtain historical equipment usage records and mark all used equipment;

[0172] According to the previously used equipment, determine the corresponding equipment architecture and obtain the previously used architecture index;

[0173] Extract commonalities from previously used architecture indicators to obtain basic general indicators;

[0174] Screening and analyzing the extracted used architecture indicators for characteristic performance indicators to obtain characteristic performance indicators;

[0175] Based on the basic general indicators and combined with the characteristic performance indicators, the platform general indicators are obtained.

[0176] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0177] According to the architecture-specific indicators, check the platform common indicators to determine whether the architecture-specific indicators are entered indicators;

[0178] In response to the judgment result being negative, the architecture-specific indicator is subjected to indicator conversion processing to obtain a specific conversion indicator, and the specific conversion indicator is added to the platform general indicator;

[0179] If the judgment result is yes, the conversion relationship between the architecture-specific indicators and the platform-general indicators is determined, and based on the conversion relationship, an indicator conversion relationship table is constructed.

[0180] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0181] Receive the original performance data of the device transmitted by the device driver interface;

[0182] Obtain the platform's general indicators and indicator conversion relationship table;

[0183] Extract fields from the original performance data of the device and the common indicators of the platform to obtain original fields and indicator fields;

[0184] According to the original field and the indicator field, the field status of the original performance data of the equipment is judged;

[0185] According to the results of field status judgment, the original performance data of the equipment is processed to obtain abstract performance data, and the indicator conversion relationship table is updated.

[0186] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0187] In response to the existence of the original field, but the corresponding indicator field does not exist for the platform general indicator, the original field is a newly added field, and a new indicator field is added to the indicator conversion relationship table, and the corresponding conversion relationship is set to no conversion;

[0188] In response to the indicator field existing, but the corresponding original field does not exist in the original performance data of the device, the indicator field is a discarded field, and the indicator field is marked as disabled in the indicator conversion relationship table;

[0189] In response to the existence of both the original field and the corresponding indicator field, performing type consistency judgment based on the field types of the original field and the corresponding indicator field;

[0190] In response to the inconsistency between the field types of the original field and the corresponding indicator field, the original field is converted into a field type, wherein the field type conversion includes at least one of the following: converting a value into a string, converting a string into a value;

[0191] In response to a successful conversion of the field type, the corresponding conversion relationship in the indicator conversion relationship table is updated, otherwise, it is marked as a conversion failure;

[0192] In response to the device original performance data completing the field status judgment and the corresponding field type conversion, the device original performance data is uniformly formatted and encapsulated into abstract performance data.

[0193] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0194] Traverse all fields in the abstract performance data to obtain abstract data fields;

[0195] Based on the name of the abstract data field, search in the indicator conversion relationship table to determine the corresponding conversion rule;

[0196] Based on the platform general indicators, the field type of the abstract data field is verified. If the verification result is inconsistent, the type of the abstract data field is converted according to the conversion rule. Otherwise, no conversion is required.

[0197] According to the conversion rules, the abstract performance data is subjected to data standardization processing and storage adaptability processing respectively to obtain the platform standard performance data, wherein the selection of storage adaptability processing is based on the type of database.

[0198] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0199] Based on common indicators, the platform standard performance data is obtained from the database for visualization output to obtain a basic dashboard;

[0200] Obtain the business type specified by the user, perform indicator analysis based on the business type, and obtain key performance indicators;

[0201] According to the key performance indicators, the corresponding common indicators in the basic dashboard are filtered to generate a recommended configuration dashboard.

[0202] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0203] Determine the device driver interface and architecture-specific indicators based on the device architecture type;

[0204] Get the platform general indicators, combine them with the architecture specific indicators, and get the indicator conversion relationship table;

[0205] Obtain the original performance data of the device through the device driver interface;

[0206] Through the preset driver isolation abstraction layer, the original performance data of the device is processed into abstract performance data;

[0207] Based on the indicator conversion relationship table, the abstract performance data is parsed and standardized to obtain the platform standard performance data, and the platform standard performance data is stored in the database.

[0208] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0209] According to the architecture-specific indicators, check the platform common indicators to determine whether the architecture-specific indicators are entered indicators;

[0210] In response to the judgment result being negative, the architecture-specific indicator is subjected to indicator conversion processing to obtain a specific conversion indicator, and the specific conversion indicator is added to the platform general indicator;

[0211] If the judgment result is yes, the conversion relationship between the architecture-specific indicators and the platform-general indicators is determined, and based on the conversion relationship, an indicator conversion relationship table is constructed.

[0212] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0213] Receive the original performance data of the device transmitted by the device driver interface;

[0214] Obtain the platform's general indicators and indicator conversion relationship table;

[0215] Extract fields from the original performance data of the device and the common indicators of the platform to obtain original fields and indicator fields;

[0216] According to the original field and the indicator field, the field status of the original performance data of the equipment is judged;

[0217] According to the results of field status judgment, the original performance data of the equipment is processed to obtain abstract performance data, and the indicator conversion relationship table is updated.

[0218] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0219] In response to the existence of the original field, but the corresponding indicator field does not exist for the platform general indicator, the original field is a newly added field, and a new indicator field is added to the indicator conversion relationship table, and the corresponding conversion relationship is set to no conversion;

[0220] In response to the indicator field existing, but the corresponding original field does not exist in the original performance data of the device, the indicator field is a discarded field, and the indicator field is marked as disabled in the indicator conversion relationship table;

[0221] In response to the existence of both the original field and the corresponding indicator field, performing type consistency judgment based on the field types of the original field and the corresponding indicator field;

[0222] In response to the inconsistency between the field types of the original field and the corresponding indicator field, the original field is converted into a field type, wherein the field type conversion includes at least one of the following: converting a value into a string, converting a string into a value;

[0223] In response to a successful conversion of the field type, the corresponding conversion relationship in the indicator conversion relationship table is updated, otherwise, it is marked as a conversion failure;

[0224] In response to the device original performance data completing the field status judgment and the corresponding field type conversion, the device original performance data is uniformly formatted and encapsulated into abstract performance data.

[0225] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0226] Traverse all fields in the abstract performance data to obtain abstract data fields;

[0227] Based on the name of the abstract data field, search in the indicator conversion relationship table to determine the corresponding conversion rule;

[0228] Based on the platform general indicators, the field type of the abstract data field is verified. If the verification result is inconsistent, the type of the abstract data field is converted according to the conversion rule. Otherwise, no conversion is required.

[0229] According to the conversion rules, the abstract performance data is subjected to data standardization processing and storage adaptability processing respectively to obtain the platform standard performance data, wherein the selection of storage adaptability processing is based on the type of database.

[0230] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0231] Based on common indicators, the platform standard performance data is obtained from the database for visualization output to obtain a basic dashboard;

[0232] Obtain the business type specified by the user, perform indicator analysis based on the business type, and obtain key performance indicators;

[0233] According to the key performance indicators, the corresponding common indicators in the basic dashboard are filtered to generate a recommended configuration dashboard.

[0234] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in the present application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0235] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, 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 specification.

[0236] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A method for managing equipment performance data, characterized in that: include: Determine the device driver interface and architecture-specific indicators based on the device architecture type; Obtaining platform general indicators and combining them with the architecture specific indicators to obtain an indicator conversion relationship table; Obtaining original performance data of the device through the device driver interface; Processing the original performance data of the device into abstract performance data through a preset driver isolation abstraction layer; Based on the indicator conversion relationship table, the abstract performance data is parsed and standardized to obtain platform standard performance data, and the platform standard performance data is stored in a database.

2. A device performance data management method according to claim 1, characterized in that: Obtain the platform general indicator, and combine it with the architecture specific indicator to obtain an indicator conversion relationship table, wherein the platform general indicator is obtained by the following method: Obtain historical equipment usage records and mark all used equipment; According to the previously used equipment, a corresponding equipment architecture is determined, and a previously used architecture indicator is obtained; Extracting commonalities from the previously used architecture indicators to obtain basic general indicators; Performing characteristic performance index screening and analysis on the extracted previously used architecture index to obtain characteristic performance index; The platform general indicators are obtained according to the basic general indicators in combination with the characteristic performance indicators.

3. A method for managing equipment performance data according to claim 1, characterized in that: Obtain the platform general indicators and combine them with the architecture specific indicators to obtain an indicator conversion relationship table, including: According to the architecture-specific indicator, a check is performed in the platform-general indicators to determine whether the architecture-specific indicator is an entered indicator; In response to a negative result of the judgment, the architecture-specific indicator is subjected to indicator conversion processing to obtain a specific conversion indicator, and the specific conversion indicator is added to the platform-general indicator; If the judgment result is yes, the conversion relationship between the architecture-specific indicator and the platform-general indicator is determined, and based on the conversion relationship, the indicator conversion relationship table is constructed.

4. A method for managing equipment performance data according to claim 1, characterized in that: The original performance data of the device is processed into abstract performance data through a preset driver isolation abstraction layer, wherein the driver isolation abstraction layer performs the following steps: Receiving the original performance data of the device transmitted by the device driver interface; Obtaining the platform general indicators and the indicator conversion relationship table; Performing field extraction on the original performance data of the device and the general indicators of the platform respectively to obtain original fields and indicator fields; According to the original field and in combination with the indicator field, the field status of the original performance data of the device is judged; According to the result of the field status judgment, the original performance data of the device is processed to obtain the abstract performance data, and the indicator conversion relationship table is updated.

5. A method for managing equipment performance data according to claim 4, characterized in that: The processing of the original performance data of the device according to the result of the field status judgment to obtain the abstract performance data and updating the indicator conversion relationship table includes: In response to the existence of the original field and the platform general indicator not having the corresponding indicator field, the original field is a newly added field, the indicator field is added to the indicator conversion relationship table, and the corresponding conversion relationship is set to no conversion; In response to the existence of the indicator field, but the original performance data of the device does not have a corresponding original field, the indicator field is a discarded field, and the indicator field is marked as disabled in the indicator conversion relationship table; In response to the existence of both the original field and the corresponding indicator field, performing type consistency judgment based on field types of the original field and the corresponding indicator field; In response to the field types of the original field and the corresponding indicator field being inconsistent, the original field is subjected to field type conversion, wherein the field type conversion includes at least one of the following: converting a value to a string, or converting a string to a value; In response to the field type conversion being successful, the corresponding conversion relationship in the indicator conversion relationship table is updated, otherwise, it is marked as conversion failure; In response to the device original performance data completing the field status judgment and the corresponding field type conversion, the device original performance data is uniformly formatted and encapsulated into the abstract performance data.

6. A method for managing equipment performance data according to claim 1, characterized in that: Based on the indicator conversion relationship table, the abstract performance data is parsed and standardized to obtain platform standard performance data, including: Traverse all fields in the abstract performance data to obtain abstract data fields; Based on the name of the abstract data field, searching in the indicator conversion relationship table to determine the corresponding conversion rule; Based on the platform general indicator, the field type of the abstract data field is verified, and in response to the verification result being inconsistent, the type of the abstract data field is converted according to the conversion rule, otherwise, no conversion is required; According to the conversion rules, the abstract performance data is subjected to data standardization processing and storage adaptability processing respectively to obtain platform standard performance data, wherein the selection of the storage adaptability processing is based on the type of the database.

7. A method for managing equipment performance data according to claim 1, characterized in that: After storing the platform standard performance data in the database, the method includes: Based on the general indicators, the standard performance data of the platform is obtained from the database for visual output to obtain a basic dashboard; Obtain the business type specified by the user, perform indicator analysis based on the business type, and obtain key performance indicators; According to the key performance indicators, the corresponding common indicators in the basic dashboard are screened to generate a recommended configuration dashboard.

8. A device for managing equipment performance data, characterized in that: The device comprises: A device identification module is used to determine the device driver interface and architecture-specific indicators according to the device architecture type; An indicator conversion relationship generation module is used to obtain the platform general indicators and combine them with the architecture specific indicators to obtain an indicator conversion relationship table; A drive data acquisition module, used to obtain original performance data of the device through the device drive interface; An isolation abstract processing module, used for processing the original performance data of the device into abstract performance data based on a preset driver isolation abstract layer; The data parsing and storage module is used to parse and standardize the abstract performance data based on the indicator conversion relationship table, obtain platform standard performance data, and store the platform standard performance data in a database.

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

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

Images