A hard disk performance test method, system, electronic device and readable storage medium
By automatically analyzing system logs and hard disk logs and selecting target performance tests, the inefficiency of SSD performance testing when tests are interrupted or fail is resolved, enabling faster and more comprehensive test results.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- INSPUR SUZHOU INTELLIGENT TECH CO LTD
- Filing Date
- 2022-06-30
- Publication Date
- 2026-06-26
Smart Images
Figure CN115129571B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of servers, and in particular to a hard disk performance testing method, system, electronic device, and readable storage medium. Background Technology
[0002] During performance testing of SSDs (Solid State Drives), if the test is interrupted or the result fails, it is impossible to quickly proceed to the next targeted test. It is necessary to wait until the performance test is completely finished, manually collect logs, and analyze the test problems and results. After judgment, the next relevant test is carried out, such as retesting or changing the test method. The overall testing efficiency is low.
[0003] Therefore, how to provide a solution to the above-mentioned technical problems is a problem that needs to be solved by those skilled in the art. Summary of the Invention
[0004] The purpose of this application is to provide a hard disk performance testing method, system, electronic device, and readable storage medium that is more accurate, reliable, and comprehensive than manual analysis, and does not require waiting until the performance test is completely finished before analysis and judgment, thereby improving the efficiency of hard disk performance testing.
[0005] To address the aforementioned technical problems, this application provides a hard disk performance testing method applied to a processing device, the performance testing method comprising:
[0006] When a hard drive performance anomaly is detected, retrieve the system log and hard drive log;
[0007] The cause of the test anomaly was determined by the system log and the hard disk log;
[0008] Select the target performance test based on the reasons for the test anomalies;
[0009] Perform the target performance test on the hard drive, and repeat the operation of obtaining system logs and hard drive logs when a performance test anomaly is detected, until the performance test result of the hard drive is obtained.
[0010] Optionally, the process of determining the cause of the test anomaly through the system log and the hard disk log includes:
[0011] The system logs and hard disk logs were used to determine the causes of multiple test anomalies;
[0012] This hard drive performance testing method also includes:
[0013] Generate prompt messages including multiple reasons for the test anomalies;
[0014] The process of selecting the target performance test based on the cause of the test anomaly includes:
[0015] Receive the test selection instruction sent by the user based on the prompt information, and determine the target performance test according to the test selection instruction.
[0016] Optionally, after determining multiple test anomaly causes through the system log and the hard disk log, the hard disk performance testing method further includes:
[0017] Based on the system logs and the hard disk logs, determine the recommended percentage of performance tests corresponding to each of the test anomaly causes;
[0018] The process of generating prompt information including multiple reasons for the test anomalies includes:
[0019] Generate prompts including multiple test anomaly causes, the corresponding performance test for each test anomaly cause, and the recommended percentage.
[0020] Optionally, while generating information including multiple test anomaly causes and corresponding performance tests and recommended percentages for each test anomaly cause, the hard disk performance testing method further includes:
[0021] Start timing and determine if the current timing time has reached the target timing time;
[0022] The process of selecting the target performance test based on the cause of the test anomaly includes:
[0023] If the current timing reaches the target timing and no test selection instruction is received from the user, the performance test with the highest recommended percentage among all recommended percentages will be used as the target performance test.
[0024] Optionally, after generating the prompt information including multiple reasons for the test anomalies, the hard disk performance testing method further includes:
[0025] The prompt information is sent to the terminal so that the user can obtain the prompt information through the terminal and send the test selection command based on the prompt information.
[0026] Optionally, the process of obtaining system logs and hard disk logs when a hard disk performance test anomaly is detected includes:
[0027] When the hard drive performance test is detected to have stopped or the result of the performance test is a failure, retrieve the system log and hard drive log.
[0028] Optionally, the target performance test includes any one of the following: multi-disk full configuration core binding test, abnormal single disk performance test, and same backplane performance test.
[0029] To address the aforementioned technical problems, this application also provides a hard disk performance testing system applied to a processing device, the performance testing system comprising:
[0030] The acquisition module is used to acquire system logs and hard drive logs when a performance test anomaly of the hard drive is detected.
[0031] The analysis module is used to determine the cause of test anomalies through the system logs and the hard disk logs;
[0032] The selection module is used to select a target performance test based on the cause of the test anomaly.
[0033] The testing module is used to perform the target performance test on the hard drive and repeat the operation of obtaining system logs and hard drive logs when a performance test anomaly is detected on the hard drive until the performance test result of the hard drive is obtained.
[0034] To address the aforementioned technical problems, this application also provides an electronic device, comprising:
[0035] Memory, used to store computer programs;
[0036] A processor, used to execute the computer program to implement the steps of the hard disk performance testing method as described in any of the above.
[0037] To address the aforementioned technical problems, this application also provides a readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the hard disk performance testing method described in any of the above descriptions.
[0038] This application provides a hard disk performance testing method applied to a processor. The performance testing method includes: when a hard disk performance test anomaly is detected, acquiring system logs and hard disk logs; determining the cause of the test anomaly through the system logs and hard disk logs; selecting a target performance test based on the cause of the test anomaly; performing the target performance test on the hard disk, and repeating the operation of acquiring system logs and hard disk logs when a hard disk performance test anomaly is detected, until the performance test result of the hard disk is obtained.
[0039] In practical applications, the solution proposed in this application captures system logs and hard disk logs by the processor when a performance test anomaly is detected. The cause of the test anomaly is analyzed based on the system logs and hard disk logs. The corresponding target performance test is then performed on the hard disk based on the analysis results. This method is more accurate, reliable, and comprehensive than manual analysis, and it does not require waiting until the performance test is completely finished before analysis and judgment, thus improving the efficiency of hard disk performance testing.
[0040] This application also provides a hard disk performance testing system, electronic device, and readable storage medium, which have the same beneficial effects as the aforementioned hard disk performance testing method. Attached Figure Description
[0041] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0042] Figure 1 A flowchart of the steps of a hard disk performance testing method provided in this application;
[0043] Figure 2 A flowchart illustrating the steps of another hard disk performance testing method provided in this application;
[0044] Figure 3 A flowchart illustrating the steps of another hard disk performance testing method provided in this application;
[0045] Figure 4 A flowchart illustrating the steps of another hard disk performance testing method provided in this application;
[0046] Figure 5 A flowchart illustrating the steps of another hard disk performance testing method provided in this application;
[0047] Figure 6 This is a schematic diagram of the structure of a hard disk performance testing system provided in this application;
[0048] Figure 7 A schematic diagram of the structure of an electronic device provided in this application;
[0049] Figure 8 This is a schematic diagram of the structure of another electronic device provided in this application. Detailed Implementation
[0050] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0051] During SSD performance testing, if the test is interrupted or fails, it's impossible to quickly proceed to the next targeted test. The process must wait until the entire performance test is complete before manually analyzing the test problems and results, leading to low efficiency in SSD performance testing. To address this efficiency issue, this application provides a new hard drive performance testing method through the following embodiments. This method is more accurate, reliable, and comprehensive than manual analysis, and eliminates the need to wait until the entire performance test is finished for analysis and judgment, thus improving hard drive performance testing efficiency.
[0052] Please refer to Figure 1 , Figure 1 The flowchart of a hard disk performance testing method provided in this application is applied to a processing device. The hard disk performance testing method includes:
[0053] S101: When a hard drive performance test anomaly is detected, retrieve the system log and hard drive log;
[0054] The hard drive can be an SSD. During SSD performance testing, if an anomaly is detected, such as test termination or failure, the system's pre-built log collection module will capture and save system logs and hard drive logs. This step involves acquiring both system and hard drive logs to ensure more accurate and comprehensive analysis results during subsequent anomaly investigation.
[0055] Of course, the hard drive can be an SSD or other types of hard drives; this application does not make any specific limitations here.
[0056] S102: Determine the cause of the test anomaly through system logs and hard disk logs;
[0057] S103: Select target performance test based on the cause of test anomalies;
[0058] Specifically, analyzing the relevant parameters in the system logs and hard disk logs can determine the possible causes of the aforementioned performance test anomalies, i.e., the test anomaly causes in S102. Each performance test anomaly cause can correspond to one or more performance tests. Performance tests include, but are not limited to, multi-disk full-configuration core-binding tests, abnormal single-disk performance tests, and same-backplane performance tests. For example, if the analysis of the system logs and hard disk logs reveals that the performance test anomaly is caused by a single-disk failure, then the target performance test corresponding to this test anomaly cause is the abnormal single-disk performance test.
[0059] S104: Perform a target performance test on the hard drive, and repeat the operation of obtaining system logs and hard drive logs when a performance test anomaly is detected, until the hard drive performance test results are obtained.
[0060] Specifically, the target performance test determined in S103 is performed on the hard drive, and then the operations of S101 to S103 are repeated until the performance test results of the hard drive are obtained. The process of obtaining the hard drive test results includes automatically summarizing and analyzing the test results through a preset number of analysis and comparison tests, and presenting the comparison differences.
[0061] As can be seen, in this embodiment, when a performance test anomaly of the hard drive is detected, the processor captures the system log and hard drive log, analyzes the cause of the test anomaly based on the system log and hard drive log, and performs the corresponding target performance test on the hard drive according to the analysis results of the test anomaly cause. This is more accurate, reliable and comprehensive than manual analysis, and there is no need to wait until the performance test is completely finished before analysis and judgment, thus improving the efficiency of hard drive performance testing.
[0062] Please refer to Figure 2 , Figure 2 A flowchart of a preferred hard disk performance testing method provided in this application includes:
[0063] S201: When a hard drive performance test anomaly is detected, retrieve the system log and hard drive log;
[0064] S202: Identify the causes of multiple test anomalies through system logs and hard disk logs;
[0065] S203: Generate a prompt message including multiple reasons for test exceptions;
[0066] S204: Receive the test selection instruction sent by the user based on the prompt information, and determine the target performance test according to the test selection instruction;
[0067] S205: Perform a target performance test on the hard drive, and repeat the operation of obtaining system logs and hard drive logs when a performance test anomaly is detected, until the hard drive performance test results are obtained.
[0068] It is understandable that hard drive performance test anomalies may be caused by multiple reasons. Therefore, when a hard drive performance test anomaly is detected, analyzing relevant parameters in the system log and hard drive log can reveal multiple possible causes. Based on the multiple test anomaly causes identified in S202, a prompt message is generated, including the specific details of the test anomaly cause, such as single disk failure, backplane malfunction, or load imbalance. The user can specifically refer to the tester. The tester selects a test anomaly cause from the prompt message. Based on the user's selection command, the target performance test is determined. For example, if the tester selects "single disk failure" from the prompt message interface, they output the test selection command corresponding to the single disk failure, and the determined target performance test is the abnormal single disk performance test.
[0069] As another optional embodiment, the prompt message may include not only possible causes of test anomalies, but also suggested performance tests for each cause. Testers can directly select a suggested performance test from the display, i.e., send a test selection command. In this embodiment, the target performance test is selected by the tester, facilitating timely connection to the hard drive for performance testing.
[0070] Please refer to Figure 3 , Figure 3 A flowchart of a preferred hard disk performance testing method provided in this application includes:
[0071] S301: When a hard drive performance test anomaly is detected, retrieve the system log and hard drive log;
[0072] S302: Identify the causes of multiple test anomalies through system logs and hard disk logs, and determine the recommended percentage of performance tests corresponding to each test anomaly cause;
[0073] S303: Generates a prompt message that includes multiple test exception reasons, the corresponding performance test for each test exception reason, and the recommended percentage;
[0074] S304: Receives the test selection instruction sent by the user based on the prompt information, and determines the target performance test according to the test selection instruction;
[0075] S305: Performs a target performance test on the hard drive and repeats the process of obtaining system logs and hard drive logs when a performance test anomaly is detected, until the hard drive performance test results are obtained.
[0076] Specifically, when identifying multiple test anomalies through system logs and hard disk logs, this embodiment also determines the likelihood of each test anomaly causing the aforementioned performance test anomalies based on the system logs and hard disk logs. Based on this, a recommended percentage is assigned to the performance test corresponding to each test anomaly. When generating prompt information, the recommended percentage can be displayed simultaneously, so that testers can select the performance test with the higher recommended percentage to send the test selection command. This reduces the process of testers analyzing multiple test anomalies and further improves the efficiency of performance testing.
[0077] Furthermore, considering the possibility of a particular test anomaly, multiple performance tests are recommended for that anomaly. Recommended percentages can be assigned to multiple performance tests corresponding to that anomaly, and the recommended percentages for each performance test can be displayed in the prompt message so that testers can select performance tests based on the recommended percentages.
[0078] For example, if the prompt message includes "Multi-disk full configuration core binding test 30%", "Abnormal single disk performance test 10%", and "Same backplane performance test 5%", the tester can directly send the test selection command corresponding to the multi-disk full configuration core binding test.
[0079] Please refer to Figure 4 , Figure 4 A flowchart of a preferred hard disk performance testing method provided in this application includes:
[0080] S401: When a hard drive performance test anomaly is detected, retrieve the system log and hard drive log;
[0081] S402: Identify the causes of multiple test anomalies through system logs and hard disk logs, and determine the recommended percentage of performance tests corresponding to each test anomaly cause;
[0082] S403: Generate a prompt message including multiple test exception reasons, the corresponding performance test for each test exception reason and its recommended percentage, and start timing;
[0083] S404: Determine whether a test selection command sent by the user has been received. If not, execute S405; if yes, execute S407.
[0084] S405: Determine whether the current timing time has reached the target timing time. If not, execute S404; if yes, execute S406.
[0085] S406: Use the performance test with the highest recommended percentage among all recommended percentages as the target performance test;
[0086] S407: Determine the target performance test based on the test selection command;
[0087] S408: Performs a target performance test on the hard drive and repeats the process of obtaining system logs and hard drive logs when a performance test anomaly is detected, until the hard drive performance test results are obtained.
[0088] Specifically, as described above, the target performance test can be a performance test selected by the user after receiving a prompt message. However, considering that users may not be able to respond to the received prompt message in a timely manner, to avoid waiting for a long time for the user to send a test selection instruction to determine the next performance test, this embodiment starts timing at the same time as generating the prompt message. If a test selection instruction sent by the user is received within the target timing time, the target performance test is determined based on the user's test selection instruction. If the current timing time reaches the target timing time and no test selection instruction has been received by the user, the performance test corresponding to a test anomaly reason is selected from multiple test anomaly reasons as the target performance test. To further improve the efficiency of performance testing, this embodiment selects the performance test corresponding to the test anomaly reason with the largest recommended percentage among the recommended percentages as the target performance test. For example, the recommended percentages for the performance tests corresponding to each test anomaly reason determined by S402 are 30% for multi-disk full configuration core-binding test, 10% for abnormal single disk performance test, and 5% for same backplane performance test. If the current timing time reaches the target timing time and no test selection instruction has been received by the user, the multi-disk full configuration core-binding test is selected as the target performance test.
[0089] The target timing time is set according to the actual test requirements, and this embodiment does not impose specific limitations on it.
[0090] Please refer to Figure 5 , Figure 5 A flowchart of a preferred hard disk performance testing method provided in this application includes:
[0091] S501: When the hard drive performance test is detected to have been aborted or the performance test result is a failure, retrieve the system log and hard drive log;
[0092] S502: Identify the causes of multiple test anomalies through system logs and hard disk logs, and determine the recommended percentage of performance tests corresponding to each test anomaly cause;
[0093] S503: Generates a prompt message that includes multiple test exception reasons, the corresponding performance test for each test exception reason, and the recommended percentage;
[0094] S504: Send a prompt message to the terminal and start timing so that the user can obtain the prompt message through the terminal and send a test selection command based on the prompt message;
[0095] S505: Determine whether a test selection command sent by the user has been received. If not, execute S506; if yes, execute S508.
[0096] S506: Determine whether the current timing time has reached the target timing time. If not, execute S505; if yes, execute S507.
[0097] S507: Use the performance test with the highest recommended percentage among all recommended percentages as the target performance test;
[0098] S508: Determines the target performance test based on the test selection command;
[0099] S509: Performs a target performance test on the hard drive and repeats the process of obtaining system logs and hard drive logs when a performance test anomaly is detected, until the hard drive performance test results are obtained.
[0100] Specifically, after generating prompts including multiple test anomaly causes and recommended performance tests and their recommended percentages for each anomaly cause, the prompts can be sent to the user's terminal to remind the user to check the prompts and understand the hard drive performance testing device. The terminal can be a mobile terminal, such as a mobile phone, iPad, or laptop. After receiving the prompts on the terminal, the user can send test selection commands remotely via SMS or email. It is understood that the solution in this embodiment allows testers to remotely control the hard drive performance testing without on-site participation, improving the flexibility of hard drive testing. Specifically, in this embodiment, timing only begins when the prompts are sent to the terminal.
[0101] In summary, after the hard drive performance test begins, if the test is interrupted or fails, the log capture module is triggered to retrieve and save the system OS logs and hard drive logs. Then, the log analysis module is triggered to determine the possible causes of the test interruption or failure based on the system OS logs and hard drive logs, and to comprehensively determine the next performance test to be performed. Each performance test is calculated as a percentage based on the probability of the problem occurring. Next, the server SMS and email notification module is triggered to send the test anomaly information and the next test operation to the testers. Testers can remotely issue test selection commands to the server command receiving module based on the fault situation, and the server will automatically execute the tests according to the commands issued by the testers. If the testers do not issue remote commands, the server will default to executing the recommended test method with the highest percentage based on the comprehensive judgment. After the test is executed, the test results are collected, summarized, and analyzed. The entire process requires no on-site participation from testers, and test execution commands can be selectively issued remotely, greatly improving testing efficiency and aiding in the analysis of test problems.
[0102] On the other hand, please refer to Figure 6 , Figure 6 This application provides a schematic diagram of a hard disk performance testing system, applied to a processing device. The performance testing system includes:
[0103] Module 11 is used to obtain system logs and hard disk logs when a performance test anomaly of the hard disk is detected;
[0104] Analysis module 12 is used to determine the cause of test anomalies through system logs and hard disk logs;
[0105] Select module 13, which is used to select target performance tests based on the cause of test anomalies;
[0106] Test module 14 is used to perform target performance tests on the hard drive and repeat the operation of obtaining system logs and hard drive logs when a performance test anomaly is detected on the hard drive until the performance test results of the hard drive are obtained.
[0107] As can be seen, in this embodiment, when a performance test anomaly of the hard drive is detected, the processor captures the system log and hard drive log, analyzes the cause of the test anomaly based on the system log and hard drive log, and performs the corresponding target performance test on the hard drive according to the analysis results of the test anomaly cause. This is more accurate, reliable and comprehensive than manual analysis, and there is no need to wait until the performance test is completely finished before analysis and judgment, thus improving the efficiency of hard drive performance testing.
[0108] As an optional implementation, the process of determining the cause of test anomalies through system logs and disk logs includes:
[0109] The causes of multiple test anomalies were identified through system logs and hard disk logs;
[0110] The hard drive performance testing system also includes:
[0111] The information generation module is used to generate prompts that include multiple reasons for test anomalies;
[0112] The process of selecting target performance tests based on the causes of test anomalies includes:
[0113] Receive test selection instructions sent by the user based on the prompt information, and determine the target performance test according to the test selection instructions.
[0114] As an optional embodiment, the analysis module 12 is also used to determine the recommended percentage of performance test corresponding to each test anomaly cause based on system logs and hard disk logs;
[0115] The process of generating a message that includes multiple reasons for test exceptions includes:
[0116] Generate prompts including multiple test exception reasons, the corresponding performance test for each test exception reason, and the recommended percentage.
[0117] As an optional embodiment,
[0118] The timing monitoring module is used to start timing while generating prompts that include multiple test anomaly reasons and the corresponding performance test and recommended percentage for each test anomaly reason, and to determine whether the current timing time has reached the target timing time.
[0119] The process of selecting target performance tests based on the causes of test anomalies includes:
[0120] If the current timing reaches the target timing and no test selection instruction is received from the user, the performance test with the highest recommended percentage among all recommended percentages will be used as the target performance test.
[0121] As an optional embodiment, the hard disk performance testing system further includes:
[0122] The sending module is used to send prompts to the terminal so that the user can obtain the prompts through the terminal and send test selection instructions based on the prompts.
[0123] As an optional implementation, when a hard drive performance anomaly is detected, the process of obtaining system logs and hard drive logs includes:
[0124] When the hard drive performance test is detected to have stopped or failed, retrieve the system log and hard drive log.
[0125] As an optional embodiment, the target performance test includes any one of the following: multi-disk full configuration core binding test, abnormal single disk performance test, and same backplane performance test.
[0126] On the other hand, please refer to Figure 7 , Figure 7 This application provides a schematic diagram of the structure of an electronic device, which includes:
[0127] Memory 21 is used to store computer programs;
[0128] Processor 22 is used to implement the steps of any of the above-described hard disk performance testing methods when executing computer programs.
[0129] Specifically, memory 21 includes a non-volatile storage medium and internal memory 21. The non-volatile storage medium stores the operating system and computer-readable instructions, and the internal memory 21 provides an environment for the operation of the operating system and computer-readable instructions in the non-volatile storage medium. When processor 22 executes the computer program stored in memory 21, it can perform the following steps: when a performance test anomaly of the hard disk is detected, obtain the system log and hard disk log; determine the cause of the test anomaly through the system log and hard disk log; select a target performance test based on the cause of the test anomaly; perform the target performance test on the hard disk, and repeat the operation of obtaining the system log and hard disk log when a performance test anomaly of the hard disk is detected, until the performance test result of the hard disk is obtained.
[0130] As can be seen, in this embodiment, when a performance test anomaly of the hard drive is detected, the processor 22 captures the system log and hard drive log, analyzes the cause of the test anomaly based on the system log and hard drive log, and performs the corresponding target performance test on the hard drive according to the analysis results of the test anomaly cause. This is more accurate, reliable and comprehensive than manual analysis, and there is no need to wait until the performance test is completely finished before analysis and judgment, thus improving the efficiency of hard drive performance testing.
[0131] As an optional embodiment, when the processor 22 executes the computer subroutine stored in the memory 21, it can perform the following steps: determine multiple test anomaly causes through system logs and hard disk logs; generate prompt information including multiple test anomaly causes; receive test selection instructions sent by the user based on the prompt information, and determine the target performance test according to the test selection instructions.
[0132] As an optional embodiment, when the processor 22 executes the computer subroutine stored in the memory 21, it can perform the following steps: determine the recommended percentage of the performance test corresponding to each test anomaly based on the system log and the hard disk log; generate a prompt message including multiple test anomaly causes and the performance test corresponding to each test anomaly cause and its recommended percentage.
[0133] As an optional embodiment, when the processor 22 executes the computer subroutine stored in the memory 21, it can perform the following steps: start timing, determine whether the current timing time has reached the target timing time; if the current timing time has reached the target timing time, and no test selection instruction sent by the user has been received, take the performance test with the largest recommended percentage among all recommended percentages as the target performance test.
[0134] As an optional embodiment, when the processor 22 executes the computer subroutine stored in the memory 21, it can perform the following steps: sending a prompt message to the terminal so that the user can obtain the prompt message through the terminal and send a test selection command based on the prompt message.
[0135] As an optional embodiment, when the processor 22 executes the computer subroutine stored in the memory 21, it can perform the following steps: when it detects that the hard disk performance test has been aborted or the performance test result is a failure, it obtains the system log and the hard disk log.
[0136] As an optional embodiment, when the processor 22 executes the computer subroutine stored in the memory 21, it can perform the following steps: select a target performance test based on the cause of the test anomaly, the target performance test including any one of the following: multi-disk full configuration core binding test, abnormal single disk performance test, and same backplane performance test.
[0137] Based on the above embodiments, please refer to the preferred implementation method. Figure 8 The electronic device also includes:
[0138] Input interface 23, connected to processor 22, is used to acquire externally imported computer programs, parameters, and instructions, and save them to memory 21 under the control of processor 22. Input interface 23 can be connected to an input device to receive parameters or instructions manually entered by the user. This input device can be a touch layer covering the display screen, or a button, trackball, or touchpad mounted on the terminal casing.
[0139] Display unit 24, connected to processor 22, is used to display data sent by processor 22. Display unit 24 can be a liquid crystal display (LCD) or an e-ink display, etc.
[0140] Network port 25, connected to processor 22, is used for communication with external terminal devices. The communication technology used for this connection can be wired or wireless, such as Mobile High Definition Link (MHL), Universal Serial Bus (USB), High Definition Multimedia Interface (HDMI), Wireless Fidelity (WiFi), Bluetooth, Bluetooth Low Energy, or IEEE 802.11s-based communication technology.
[0141] On the other hand, this application also provides a readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the hard disk performance testing method as described above.
[0142] Specifically, the storage medium can include various media capable of storing program code, such as USB flash drives, external hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks. The storage medium stores a computer program, which, when executed by the processor, performs the following steps: when a performance test anomaly is detected on the hard drive, the system log and hard drive log are retrieved; the cause of the anomaly is determined using the system log and hard drive log; a target performance test is selected based on the cause of the anomaly; the target performance test is performed on the hard drive, and the process of retrieving the system log and hard drive log when a performance test anomaly is detected is repeated until the hard drive performance test result is obtained.
[0143] As can be seen, in this embodiment, when a performance test anomaly of the hard drive is detected, the processor captures the system log and hard drive log, analyzes the cause of the test anomaly based on the system log and hard drive log, and performs the corresponding target performance test on the hard drive according to the analysis results of the test anomaly cause. This is more accurate, reliable and comprehensive than manual analysis, and there is no need to wait until the performance test is completely finished before analysis and judgment, thus improving the efficiency of hard drive performance testing.
[0144] As an optional embodiment, when the computer subroutine stored in the readable storage medium is executed by the processor, it can specifically perform the following steps: determine multiple test anomaly causes through system logs and hard disk logs; generate prompt information including multiple test anomaly causes; receive test selection instructions sent by the user based on the prompt information, and determine the target performance test according to the test selection instructions.
[0145] As an optional embodiment, when the computer subroutine stored in the readable storage medium is executed by the processor, it can specifically perform the following steps: determine the recommended percentage of the performance test corresponding to each test anomaly based on the system log and the hard disk log; generate a prompt message including multiple test anomaly causes and the performance test corresponding to each test anomaly cause and its recommended percentage.
[0146] As an optional embodiment, when the computer subroutine stored in the readable storage medium is executed by the processor, it can specifically implement the following steps: start timing, determine whether the current timing time has reached the target timing time; if the current timing time has reached the target timing time, and no test selection instruction sent by the user has been received, take the performance test with the largest recommended percentage among all recommended percentages as the target performance test.
[0147] As an optional embodiment, when a computer subroutine stored in a readable storage medium is executed by a processor, it can specifically perform the following steps: sending a prompt message to a terminal so that the user can obtain the prompt message through the terminal and send a test selection command based on the prompt message.
[0148] As an optional embodiment, when a computer subroutine stored in a readable storage medium is executed by a processor, the following steps can be implemented: when it is detected that the hard disk performance test has been aborted or the result of the performance test is a failure, the system log and the hard disk log are obtained.
[0149] As an optional embodiment, when a computer subroutine stored in a readable storage medium is executed by a processor, the following steps can be implemented: selecting a target performance test based on the cause of the test anomaly, wherein the target performance test includes any one of the following: multi-disk full configuration core binding test, abnormal single disk performance test, and same backplane performance test.
[0150] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0151] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A hard disk performance testing method, characterized in that, Applied to processing devices, this performance testing method includes: When a hard drive performance anomaly is detected, retrieve the system log and hard drive log; The cause of the test anomaly was determined by the system log and the hard disk log; A target performance test is selected based on the cause of the test anomaly; the target performance test is at least one of all the performance tests performed on the hard drive. Perform the target performance test on the hard drive, and repeat the operation of obtaining system logs and hard drive logs when a performance test anomaly is detected on the hard drive, until the performance test result of the hard drive is obtained; The process of determining the cause of test anomalies through the system logs and the hard disk logs includes: The system logs and hard disk logs were used to determine the causes of multiple test anomalies; This hard drive performance testing method also includes: Generate prompt messages including multiple reasons for the test anomalies; The process of selecting the target performance test based on the cause of the test anomaly includes: Receive the test selection instruction sent by the user based on the prompt information, and determine the target performance test according to the test selection instruction; After determining the causes of multiple test anomalies through the system log and the hard disk log, the hard disk performance testing method further includes: For each of the aforementioned test anomalies, based on the probability of the test anomaly caused by the test anomaly determined by the system log and the hard disk log, a recommended percentage is assigned to each performance test corresponding to the test anomaly cause. The process of generating prompt information including multiple reasons for the test anomalies includes: Generate prompts including multiple test anomaly causes, the corresponding performance test for each test anomaly cause, and the recommended percentage.
2. The hard disk performance testing method according to claim 1, characterized in that, The hard disk performance testing method also includes generating information such as multiple test anomaly causes, performance tests corresponding to each test anomaly cause, and recommended percentage prompts, while simultaneously generating the following: Start timing and determine if the current timing time has reached the target timing time; The process of selecting the target performance test based on the cause of the test anomaly includes: If the current timing reaches the target timing and no test selection instruction is received from the user, the performance test with the highest recommended percentage among all recommended percentages will be used as the target performance test.
3. The hard disk performance testing method according to claim 1, characterized in that, After generating the prompt information including multiple reasons for the test anomalies, the hard disk performance testing method further includes: The prompt information is sent to the terminal so that the user can obtain the prompt information through the terminal and send the test selection command based on the prompt information.
4. The hard disk performance testing method according to claim 1, characterized in that, The process of obtaining system logs and hard disk logs when a hard disk performance test anomaly is detected includes: When the hard drive performance test is detected to have stopped or the result of the performance test is a failure, retrieve the system log and hard drive log.
5. The hard disk performance testing method according to any one of claims 1-4, characterized in that, The target performance test includes any one of the following: multi-disk full configuration core binding test, abnormal single disk performance test, and same backplane performance test.
6. A hard disk performance testing system, characterized in that, This performance testing system, applied to processing devices, includes: The acquisition module is used to acquire system logs and hard drive logs when a performance test anomaly of the hard drive is detected. The analysis module is used to determine the cause of test anomalies through the system logs and the hard disk logs; The selection module is used to select a target performance test based on the cause of the test anomaly; the target performance test is at least one of all the performance tests performed on the hard drive. The testing module is used to perform the target performance test on the hard drive and repeat the operation of obtaining system logs and hard drive logs when a performance test anomaly of the hard drive is detected, until the performance test result of the hard drive is obtained; The process of determining the cause of test anomalies through the system logs and the hard disk logs includes: The system logs and hard disk logs were used to determine the causes of multiple test anomalies; The hard drive performance testing system also includes: The information generation module is used to generate prompt information including multiple reasons for the test anomalies; The process of selecting the target performance test based on the cause of the test anomaly includes: Receive the test selection instruction sent by the user based on the prompt information, and determine the target performance test according to the test selection instruction; The analysis module is also used to assign a recommended percentage to each performance test corresponding to each test anomaly cause, based on the probability of the test anomaly cause causing the performance test anomaly determined by the system log and the hard disk log. The process of generating prompt information including multiple reasons for the test anomalies includes: Generate prompts including multiple test anomaly causes, the corresponding performance test for each test anomaly cause, and the recommended percentage.
7. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the hard disk performance testing method as described in any one of claims 1-5 when executing the computer program.
8. A readable storage medium, characterized in that, The readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the hard disk performance testing method as described in any one of claims 1-5.