Solid state disk one-key steady state test method and system based on configuration import
By generating and importing steady-state configuration files during solid-state drive performance testing, the problem of excessively long write pre-embedded operations was solved, enabling rapid steady-state reconstruction and efficient performance testing, thereby improving testing efficiency and result reliability.
Patent Information
- Application Number
- CN202511797199.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-02
- Publication Date
- 2026-03-03
AI Technical Summary
In current solid-state drive performance testing, the write pre-embedded operation takes too long, resulting in a lengthy testing cycle, which affects R&D verification costs and product iteration speed.
By controlling the benchmark solid-state drive to perform write pre-embedded operations, the steady-state composition information is extracted to generate a configuration file, which is then imported into the target hard drive under test to achieve rapid steady-state reconstruction and performance testing.
Significantly shorten testing time, improve testing efficiency, reduce costs, ensure the accuracy and consistency of test results, and support rapid product iteration.
Smart Images
Figure CN121597504A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of solid-state drive performance testing technology, and in particular to a one-click steady-state testing method and system for solid-state drives based on configuration import. Background Technology
[0002] With the continuous advancement of flash memory technology, QLC NAND flash memory has gained widespread adoption in high-capacity solid-state drive (SSD) products due to its high storage density and cost advantages. However, QLC flash memory technology has significant limitations, including lower write operation speeds, limited program / erase cycle life, and unstable performance under non-steady-state conditions. In SSD performance evaluation, to obtain reliable and consistent test data, the device under test must be placed in a stable and controllable operating state, i.e., a steady-state environment. A steady-state state requires the physical storage area of the SSD to be fully filled with valid data, while background management functions such as garbage collection mechanisms and wear leveling algorithms are fully activated, and overall input / output performance exhibits a stable trend.
[0003] Currently, the industry generally relies on write pre-embedding technology to achieve steady-state construction, mainly employing two operation modes: sequential write pre-embedding and random write pre-embedding. Sequential write pre-embedding requires performing at least two complete sequential data writes to the entire user-addressable space of the SSD; random write pre-embedding, after completing sequential write pre-embedding, further performs multiple rounds of random data write operations to simulate real-world application scenarios and exacerbate storage fragmentation. For modern high-capacity QLC SSD products, the above write pre-embedding process often takes tens of hours or even days, resulting in an exceptionally long testing cycle. This inefficient testing method not only significantly increases R&D verification costs but also severely hinders product iteration speed and production efficiency, becoming a key obstacle that urgently needs to be overcome in the SSD performance testing process. Summary of the Invention
[0004] The purpose of this application is to propose a one-click steady-state testing method and system for solid-state drives based on configuration import, so as to improve the performance testing efficiency of solid-state drives.
[0005] To address the aforementioned technical problems, this application provides a one-click steady-state testing method for solid-state drives based on configuration import, comprising: Control the benchmark solid-state drive to perform write pre-embedding operations until the benchmark solid-state drive reaches the target test steady state; Steady-state configuration information is extracted from the controller of the reference solid-state drive, and a steady-state configuration file is generated based on the steady-state configuration information. The steady-state configuration file is then stored in the configuration file library. The target steady-state configuration file is determined from the configuration file library and imported into the target solid-state drive under test in its initial state, so that the firmware of the target solid-state drive under test is rebuilt to the target test steady state based on the steady-state configuration file. The pre-set performance test items are executed on the reconstructed target solid-state drive to obtain the target test results.
[0006] To address the aforementioned technical problems, embodiments of this application provide a one-click stable state testing system for solid-state drives based on configuration import, comprising: The write pre-embedded operation module is used to control the reference solid-state drive to perform write pre-embedded operations until the reference solid-state drive reaches the target test steady state; A steady-state configuration file generation module is used to extract steady-state composition information from the controller of the reference solid-state drive, generate a steady-state configuration file based on the steady-state composition information, and store the steady-state configuration file in a configuration file library; The solid-state drive reconstruction module is used to determine the target steady-state configuration file from the configuration file library and import the target steady-state configuration file into the target solid-state drive under test in the initial state, so that the firmware of the target solid-state drive under test is reconstructed to the target test steady state based on the steady-state configuration file; The performance testing module is used to perform preset performance tests on the reconstructed target solid-state drive and obtain the target test results.
[0007] This invention provides a one-click steady-state testing method and system for solid-state drives (SSDs) based on configuration import. The method includes: controlling a benchmark SSD to perform a write pre-embedding operation until the benchmark SSD reaches a target test steady state; extracting steady-state configuration information from the controller of the benchmark SSD and generating a steady-state configuration file based on the steady-state configuration information, storing the steady-state configuration file in a configuration file library; determining a target steady-state configuration file from the configuration file library and importing the target steady-state configuration file into a target SSD under test in its initial state, so that the firmware of the target SSD under test is reconstructed to the target test steady state based on the steady-state configuration file; and performing preset performance tests on the reconstructed target SSD under test to obtain the target test result. This invention, by extracting the steady-state configuration information of the benchmark SSD to generate a configuration file and importing it into the target device under test, quickly reconstructs the steady-state environment, avoiding the long waiting time of traditional write pre-embedding operations. It has the advantages of significantly shortening test time, improving test efficiency, reducing R&D verification costs, and accelerating product iteration. Attached Figure Description
[0008] To more clearly illustrate the solutions in this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0009] Figure 1 This is a flowchart illustrating the implementation of the one-click steady-state testing method for solid-state drives based on configuration import provided in this application embodiment. Figure 2 This is the overall flowchart of the one-click steady-state test method for solid-state drives based on configuration import provided in the embodiments of this application; Figure 3 This is a system structure block diagram provided in the embodiments of this application; Figure 4 This is a flowchart illustrating the implementation of the first sub-process in the one-click steady-state testing method for solid-state drives based on configuration import provided in this application embodiment; Figure 5 This is a flowchart illustrating the implementation of the second sub-process in the one-click steady-state testing method for solid-state drives based on configuration import provided in this application embodiment; Figure 6 This is a flowchart illustrating the implementation of the third sub-process in the one-click steady-state testing method for solid-state drives based on configuration import provided in this application embodiment; Figure 7 This is a flowchart illustrating the implementation of the fourth sub-process in the one-click steady-state testing method for solid-state drives based on configuration import provided in this application embodiment; Figure 8 This is a flowchart illustrating the implementation of the fifth sub-process in the one-click steady-state testing method for solid-state drives based on configuration import provided in this application embodiment; Figure 9 This is a schematic diagram of a one-click steady-state testing system for solid-state drives based on configuration import provided in an embodiment of this application. Detailed Implementation
[0010] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein in the specification of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having," and any variations thereof, in the specification, claims, and foregoing drawings of this application, are intended to cover non-exclusive inclusion. The terms "first," "second," etc., in the specification, claims, or foregoing drawings of this application are used to distinguish different objects, not to describe a particular order.
[0011] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.
[0012] This application proposes a one-click steady-state testing method for solid-state drives (SSDs) based on configuration import, comprising: controlling a reference SSD to perform a write pre-embedding operation until the reference SSD reaches a target test steady state; extracting steady-state configuration information from the controller of the reference SSD, generating a steady-state configuration file based on the steady-state configuration information, and storing the steady-state configuration file in a configuration file library; determining a target steady-state configuration file from the configuration file library, and importing the target steady-state configuration file into the target SSD under test in its initial state, so that the firmware of the target SSD under test is reconstructed to the target test steady state based on the steady-state configuration file; and performing preset performance test items on the reconstructed target SSD under test to obtain the target test result.
[0013] The process of controlling the benchmark SSD to perform pre-written operations can be understood as bringing the benchmark SSD into a stable working state through a specific data writing method. Specifically, this can be achieved by simulating data writing patterns in real-world usage scenarios, such as writing data in fixed-size blocks continuously or writing data according to a preset random distribution pattern. The main purpose is to ensure the benchmark SSD reaches a reproducible steady-state environment before testing. Furthermore, the process of extracting steady-state composition information from the benchmark SSD's controller can be implemented in various ways, such as reading the status values of the controller's internal registers or parsing key parameters in the controller's log file. The aim is to obtain key data reflecting the current steady state. As a preferred implementation, generating a steady-state configuration file can be achieved by converting the extracted information into a standardized format, such as JSON or XML, for subsequent storage and retrieval. Additionally, storing the steady-state configuration file in a configuration file library can be implemented using a distributed storage system to improve the efficiency and reliability of file management.
[0014] The working principle of this embodiment is as follows: First, a write pre-embedding operation is performed on the reference solid-state drive (SSD) until it reaches the target test steady state. Although this process is time-consuming, it only needs to be performed once on the reference SSD, thus providing a foundation for subsequent steady-state extraction. Further, steady-state composition information is extracted from the controller of the reference SSD, and a steady-state configuration file is generated based on this information. The generated steady-state configuration file is stored in the configuration file library, thereby achieving standardized recording and saving of the steady-state state, allowing the steady-state state to be reused without repeating the write pre-embedding operation. Specifically, the steady-state configuration file contains key state information of the reference SSD in the steady state. This information reflects the activation status of background mechanisms such as garbage collection and wear leveling, as well as the characteristic of performance stabilization. Subsequently, the target steady-state configuration file is determined from the configuration file library and imported into the target SSD in its initial state, enabling the firmware of the target SSD to be quickly rebuilt to the target test steady state based on the steady-state configuration file. The target SSD skips the time-consuming write pre-embedding process directly by importing the configuration file, significantly shortening the time required to reach the steady state. As a preferred implementation, after importing the configuration file, the firmware of the target SSD under test can quickly adjust key parameters such as the internal logical-to-physical address mapping table and flash block status information according to the information in the configuration file, thereby achieving rapid steady-state reconstruction. Finally, preset performance tests are performed on the reconstructed target SSD under test to obtain the target test results. This step ensures that the performance test is conducted on the basis that the target SSD under test has reached a steady state, thus guaranteeing the accuracy and repeatability of the test results. For example, after the steady-state reconstruction is completed, performing a verification write operation on the target SSD under test and detecting the write latency can further confirm the success of the steady-state reconstruction, thereby improving the reliability of the test process.
[0015] In summary, this application's embodiments establish a steady-state baseline through baseline write pre-embedding, reuse the steady-state state by extracting and storing configuration files, and achieve rapid steady-state reconstruction of the target SSD through configuration file import. Finally, performance testing is performed after reconstruction to obtain test results under steady-state conditions. The overall technical solution effectively solves the problem of low testing efficiency caused by excessively long write pre-embedding process in SSD steady-state testing, while ensuring the accuracy and consistency of test results.
[0016] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.
[0017] Please see Figures 1 to 3 , Figure 1 This paper illustrates a specific implementation of a one-click steady-state testing method for solid-state drives based on configuration import. Figure 2 This is the overall flowchart of the one-click steady-state test method for solid-state drives based on configuration import provided in the embodiments of this application. Figure 3 This is a system structure block diagram provided in the embodiments of this application.
[0018] It should be noted that if substantially the same result is obtained, the method of this invention does not necessarily require further clarification. Figure 1 Limited to the sequence shown, this method includes the following steps: S1: Control the reference solid-state drive to perform a write pre-embedded operation until the reference solid-state drive reaches the target test steady state.
[0019] Please see Figure 4 , Figure 4 A specific implementation of step S1 is shown below: S11: Perform a secure erase operation on the reference solid-state drive to bring it to its initial state. S12: Control the reference solid-state drive to perform write pre-embedding operations through sequential write pre-embedding and random write pre-embedding operations until the reference solid-state drive reaches the target test steady state.
[0020] Secure erase refers to an operation that completely erases all user data and internal state from a solid-state drive (SSD). In practical applications, this can be achieved through hardware reset commands or specific software tools. Its purpose is to ensure the baseline SSD returns to its factory initial state, thus providing a clean environment for subsequent write pre-wiring and significantly reducing additional time consumption caused by data fragmentation or background mechanism interference. Sequential write pre-wiring is a method of continuously writing data to the SSD. It can be implemented using single-threaded or multi-threaded large-block data stream writing, aiming to quickly fill the entire user space and efficiently cover the physical storage area using the high throughput of continuous writes. Random write pre-wiring is a writing method that simulates real-world usage scenarios. It can be implemented using multi-threaded random distribution of small-block data writing, aiming to specifically introduce fragmented data patterns and accelerate the activation of background mechanisms such as garbage collection and wear leveling.
[0021] Specifically, firstly, a secure erase operation is performed on the baseline SSD to ensure the consistency of the pre-embedding starting point, avoiding redundancy in the pre-embedding process caused by historical data residue. Based on this, sequential write pre-embedding quickly fills the entire user space, reducing the number of iterations required for random writes. Simultaneously, random write pre-embedding introduces a targeted fragmented data pattern, accelerating the activation of background mechanisms such as garbage collection and wear leveling, allowing performance fluctuations to converge to a stable state more quickly. This combined approach, based on the logic of sequential writes laying the space foundation and random writes activating the mechanism characteristics, avoids the limitations of a single pre-embedding method, thus significantly shortening the pre-embedding time while ensuring steady-state quality. For large-capacity QLC SSDs, this method effectively solves the inefficiency problem caused by the lack of standardized initial state preparation and pre-embedding method combinations in existing technologies, significantly improving the testing pace. This application's embodiment not only solves the problem of lacking standardized initial state preparation for write pre-embedding operations but also optimizes the combination strategy of pre-embedding methods, thereby achieving the technical effect of significantly shortening the pre-embedding time while ensuring steady-state quality.
[0022] S2: Extract steady-state configuration information from the controller of the reference solid-state drive, generate a steady-state configuration file based on the steady-state configuration information, and store the steady-state configuration file in the configuration file library.
[0023] Please see Figure 5 , Figure 5 A specific implementation of step S2 is shown below: S21: Extract the steady-state configuration information from the controller of the benchmark solid-state drive using a first NVMe management command or a first vendor-defined command. S22: Encode the steady-state configuration information into a binary file to generate the steady-state configuration file. S23: Store the steady-state configuration file in the configuration file library.
[0024] The first NVMe management command refers to the instruction set defined by the NVMe protocol standard for interacting with the solid-state drive (SSD) controller. It can be implemented using a standardized NVMe management interface to ensure compatibility with mainstream SSD controllers. The first vendor-defined command can be understood as a dedicated instruction developed by a specific manufacturer based on the characteristics of its own device. It can be implemented through proprietary protocol extensions to adapt to specific SSD controller models. Steady-state configuration information refers to key data reflecting the internal state of the SSD. It can include at least one of the following: logical-to-physical address mapping table, flash block status information, garbage collection module status information, and wear leveling module status information. Its purpose is to comprehensively describe the steady-state characteristics of the SSD. A binary file is a file format that stores data in binary format. It can be generated using efficient serialization technology to reduce file size and improve processing efficiency.
[0025] Specifically, key bottlenecks in the steady-state configuration file generation process are resolved through standardized extraction methods, efficient encoding mechanisms, and structured storage flows. When extracting steady-state composition information, the use of either the first NVMe management command or the first vendor-defined command not only ensures broad compatibility with SSD controllers from different manufacturers but also achieves a balance between universality and flexibility, thus avoiding extraction failures due to interface differences. When generating the steady-state configuration file, the adoption of binary encoding significantly reduces file storage and transmission overhead, providing fundamental support for subsequent rapid parsing and reconstruction of the steady-state configuration. Furthermore, the generated steady-state configuration files are centrally stored in a configuration file library, ensuring file retrieval and callability through a unified management mechanism, avoiding data security risks and management chaos that may arise from scattered storage. Overall, these technical measures work together to form an efficient and reliable one-click steady-state testing process, directly supporting the improvement of testing efficiency.
[0026] This application embodiment combines the execution of write pre-embedded operations and performance test items, further optimizing the overall process of solid-state drive steady-state testing. Through standardized extraction of steady-state composition information and efficient generation of steady-state configuration files, not only is the steady-state reconstruction time shortened, but the accuracy and repeatability of test results are also improved, thereby effectively solving the problem of low testing efficiency in existing technologies.
[0027] Furthermore, the steady-state configuration information is at least one of the following: a logical-to-physical address mapping table, flash memory block status information, garbage collection module status information, and wear leveling module status information.
[0028] The logical-to-physical address mapping table records the correspondence between data storage locations in flash memory. It can be implemented using a hash table or a tree structure, aiming to ensure accurate data distribution recovery during reconstruction. Flash block status information is a data set describing the current usage of each flash block. It can be implemented using a bitmap or state matrix, aiming to initialize the actual state of the flash blocks to support subsequent operations. Garbage collection module status information reflects the progress and strategy of background garbage collection. It can be implemented using a queue or priority list, aiming to quickly activate garbage collection behavior. Wear leveling module status information reflects the flash memory lifetime control status. It can be implemented using a counter or distribution map, aiming to maintain the uniformity of wear distribution.
[0029] Specifically, by clearly defining the content of steady-state constituent information, the problem of inaccurate reconstruction caused by incomplete information extraction is solved. The logical-to-physical address mapping table, as a core element, effectively avoids read / write path errors during the reconstruction phase, thus maintaining data consistency. Flash block status information, through initializing parameters such as erase / write cycles and the proportion of valid data, enables garbage collection and wear leveling mechanisms to run from the real historical starting point, simulating the physical characteristics of flash memory. Garbage collection module status information, by describing the background collection progress, directly improves performance stability. Wear leveling module status information, by regulating lifetime, prevents sudden performance drops caused by excessive local wear. The design of limiting information to "at least one" allows for flexible selection of necessary information types based on the test scenario. For example, when focusing on random write tests, garbage collection status can be prioritized, reducing the overhead of redundant data extraction while ensuring the integrity of critical states. This design not only improves testing efficiency but also ensures the reliability and repeatability of test results, reflecting a balance between practicality and accuracy.
[0030] Please see Figure 6 , Figure 6 A specific implementation of step S23 is shown below: S231: Encrypt and sign the steady-state configuration file to obtain an encrypted steady-state configuration file. S232: Store the encrypted steady-state configuration file in the configuration file library and associate the encrypted steady-state configuration file with the model, firmware version, and test scenario of the benchmark solid-state drive.
[0031] Encryption refers to transforming the content of the stable configuration file using a specific algorithm, making it impossible to read or tamper with without authorization. In practice, encryption can be implemented using symmetric encryption algorithms (such as AES) or asymmetric encryption algorithms (such as RSA), aiming to ensure the confidentiality of file content and prevent the leakage of sensitive information. Data signing refers to generating unique identification information for a file using digital signature technology to verify its integrity and source reliability. In practice, data signatures can be generated using a hash function combined with private key encryption, aiming to ensure that the file has not been illegally modified and its source is trustworthy. Association refers to binding the encrypted stable configuration file with the model, firmware version, and test scenario of the benchmark solid-state drive, forming a multi-dimensional context identifier. In practice, association can be achieved through database indexes, metadata tags, or file naming rules, aiming to ensure that the configuration file can accurately match the corresponding hardware and test conditions during subsequent import.
[0032] Specifically, by introducing encryption and data signature mechanisms, a secure storage system was constructed, effectively addressing the vulnerability of steady-state configuration files to attacks. Building upon this, the matching accuracy of the configuration files was further improved by associating the encrypted steady-state configuration files with the model, firmware version, and test scenario of the benchmark SSD. For example, during storage, the extracted steady-state composition information is first encrypted into a binary file, then a data signature is generated and appended to the file. Finally, the file is stored in the configuration file library while recording its associated parameters. This process not only ensures the security of the file content but also provides a reliable matching basis for subsequent import into the target SSD under test. Furthermore, the introduction of encryption and association operations avoids reconstruction failures caused by firmware version differences or incompatible test scenarios, thus significantly improving the stability of the testing process and the consistency of results.
[0033] The embodiments of this application not only enhance the security protection capability of the steady-state configuration file, but also achieve accurate matching between the file and the test conditions, thereby effectively solving the technical problems of easy tampering of configuration files and inaccurate matching in the prior art.
[0034] S3: Determine the target steady-state configuration file from the configuration file library, and import the target steady-state configuration file into the target solid-state drive under test in the initial state, so that the firmware of the target solid-state drive under test is rebuilt to the target test steady state based on the steady-state configuration file.
[0035] Please see Figure 7 , Figure 7 A specific implementation of step S3 is shown below: S31: Perform a secure erase operation on the target SSD under test to bring it to its initial state. S32: In the software interface of the test execution module, determine the target steady-state configuration file from the configuration file library. S33: Import the target steady-state configuration file into a designated memory or flash memory area of the controller of the target SSD under test using a second NVMe management command or a second vendor-defined command, so that the firmware of the target SSD under test is rebuilt to the target test steady state based on the steady-state configuration file.
[0036] The secure erase operation refers to an operation that completely erases all user data and metadata within the solid-state drive (SSD). This can be achieved using ATA secure erase commands, NVMe formatting commands, or vendor-specific full erase commands. Its purpose is to ensure the target SSD enters a completely initial state, preventing residual data from interfering with the subsequent steady-state reconstruction process. The software interface of the test execution module refers to a user interface providing graphical or command-line interaction capabilities. This can be a web-based management platform, a desktop application, or a control terminal for an embedded system. Its purpose is to provide users with a convenient way to select configuration files and reduce human error. The second NVMe management command refers to standardized management commands that conform to the NVMe protocol specification. These can be specific field combinations from Vendor Specific Commands or extended Admin Command Sets, aiming to ensure the compatibility and reliability of data import through industry-standard protocols.
[0037] Specifically, the process begins by performing a secure erase operation on the target SSD to ensure it is in an initial state free of any historical data residue, thus providing a clean foundation for subsequent steady-state reconstruction. Based on this, testers can intuitively select a matching target steady-state configuration file from the configuration file library through the test execution module's software interface. This process not only improves operational convenience but also effectively reduces the risk of configuration errors caused by human error. Subsequently, using a second NVMe management command or a second vendor-defined command, the selected steady-state configuration file is transmitted to a designated memory or flash memory area of the target SSD controller. This standardized import method ensures data transmission integrity and device compatibility, enabling the firmware to accurately parse the configuration information and efficiently complete steady-state reconstruction. Furthermore, the above method, combined with basic steps such as write pre-embedding operations and steady-state configuration information extraction, constitutes a complete steady-state testing process, significantly optimizing test efficiency and result reliability.
[0038] Furthermore, after step S32, this application also provides a specific embodiment: determining whether the firmware version of the target steady-state configuration file is consistent with the firmware version of the reference solid-state hard drive recorded in the configuration file; if they are inconsistent, an error message is returned.
[0039] The firmware version consistency verification mechanism refers to a technical means of ensuring compatibility by comparing the firmware version information in the target steady-state configuration file with the firmware version information recorded during storage on the baseline solid-state drive. This is achieved by reading metadata fields in the configuration file and performing precise matching, aiming to avoid parsing logic conflicts or reconstruction failures caused by version differences. In practical applications, error messages can be returned through pop-up prompts, log recordings, or alarm signals, with the purpose of immediately intercepting incompatibility situations and preventing the execution of subsequent invalid operations.
[0040] Specifically, after selecting the target steady-state configuration file in the test execution module's software interface, the system automatically extracts the firmware version information associated with that configuration file and compares it with the firmware version of the benchmark SSD. This timing ensures that the version check occurs at a critical point after the user confirms the configuration file but before the actual import operation, thus avoiding the triggering of an invalid import process. If a version inconsistency is detected, the system will immediately return an error message and terminate subsequent operations. This proactive error detection mechanism significantly improves the robustness of the test process while reducing resource waste and duplicate testing caused by version conflicts. Furthermore, using the benchmark SSD firmware version recorded in the configuration file library as a reference, rather than relying on the real-time state of the target SSD, further enhances the objectivity and accuracy of the comparison.
[0041] This application embodiment effectively solves the problem of test process interruption caused by firmware version mismatch by introducing a firmware version consistency verification mechanism, thus ensuring the reliability and test efficiency of steady-state reconstruction.
[0042] S4: Perform preset performance tests on the reconstructed target solid-state drive to obtain the target test results.
[0043] Please see Figure 8 , Figure 8 A specific implementation method prior to step S4 is shown below in detail: S41: Perform a verification write operation on the target SSD under test and detect the write latency of the target SSD under test to obtain the latency result. S42: If the latency result is within a preset steady-state latency threshold range, the steady-state reconstruction is determined to be successful. S43: If the latency result is not within the preset steady-state latency threshold range, the reconstruction is determined to have failed and the test process is terminated.
[0044] Verification write operations are lightweight write operations used to quickly obtain the current state information of the target SSD under test. They can be implemented through sequential or random writing of small data blocks, aiming to quickly reflect the current performance characteristics of the target SSD through minimal data interaction. Latency results can be understood as the time response characteristics exhibited by the target SSD during verification write operations, directly reflecting the activation level of garbage collection and wear leveling mechanisms. The preset steady-state latency threshold range is a numerical range set based on the actual latency characteristics of the benchmark SSD under the target test steady state. It can be determined using statistical analysis or experimental calibration methods to ensure consistency between the reconstructed state and the preset steady-state standard.
[0045] Specifically, by embedding a verification mechanism before performance testing, the problem of invalid tests caused by unreliable steady-state reconstruction is effectively solved. First, a verification write operation is performed on the target SSD under test. This process, based on the characteristic that write latency should be stable within a specific range under steady-state conditions, avoids the time-consuming full write pre-embedding process, thus significantly shortening the time required for state verification. Subsequently, the latency result is obtained by detecting the write latency and used as the core judgment criterion. Because the garbage collection and wear leveling mechanisms of the SSD are fully activated in steady state, the write latency fluctuation is small and predictable, while the latency in non-steady-state conditions is easily affected by fragmentation and fluctuates drastically. Therefore, the latency result can accurately reflect whether the current state has reached the target steady state. If the latency result is within the preset steady-state latency threshold range, the steady-state reconstruction is considered successful. This mechanism ensures that the test process continues only after successful steady-state reconstruction, thereby improving overall test efficiency and result reliability. If the delay result is not within the preset steady-state delay threshold range, the reconstruction is determined to have failed and the test process is terminated. This promptly blocks the execution of invalid tests, prevents resources from being wasted on non-steady-state data acquisition, and facilitates quick retry of reconstruction or troubleshooting of configuration issues, significantly reducing the additional time overhead caused by repeated testing.
[0046] This application's embodiments, combined with the aforementioned process of extracting steady-state composition information from a benchmark solid-state drive to generate a steady-state configuration file, further improve the reliability and efficiency of the testing system. By introducing a verification write operation and a latency detection mechanism before performance testing, not only is the success rate of steady-state reconstruction ensured, but the number of invalid tests caused by reconstruction failures is also significantly reduced, thereby optimizing the time cost and technical complexity of the entire testing process.
[0047] In one specific embodiment, suppose we need to perform a steady-state random write performance test on a 32TB QLC SSD. The existing method is as follows: 1. Securely erase the SSD; 2. Perform two full-disk sequential writes (bandwidth calculated at 3GB / s), taking approximately 10 hours; 3. Perform random writes until the performance curve stabilizes, taking approximately 10 hours; 4. Begin the performance test. The entire testing process using the existing method takes approximately 20 hours in total.
[0048] The method used in this application is as follows: 1. (Pre-configured, only required once) Using a "baseline disk" of the same model, it takes 20 hours to reach a steady state using traditional methods, and the SteadyState_Config_v1.bin file is exported. 2. Steps for all subsequent tested disks: a. Securely erase the tested SSD, taking 1 minute; b. Select the SteadyState_Config_v1.bin file in the test software interface and click the "Apply Steady State" button; c. The test software writes the configuration file data to the SSD at high speed using NVMe vendor-specific commands. This process takes approximately 2 minutes (depending on file size and interface speed); d. The software performs a short random write verification to confirm that the latency has reached a steady state level (e.g., from the initial millisecond level to the steady state level of hundreds of microseconds), taking 30 seconds; e. Immediately begin the formal random write performance test. The entire testing process using the method used in this application takes approximately 3.5 minutes in total. The comparison shows that this application reduces the preparation time for each test from 20 hours to 3.5 minutes, improving efficiency by more than 340 times. Therefore, the embodiments of this application can effectively improve testing efficiency.
[0049] Compared with the prior art, the embodiments of this application have the following significant advantages: 1. Significantly improves testing efficiency: Reduces write pre-embedding time from hours to days to minutes. The configuration import process involves only data transfer and state reconstruction, making it extremely fast.
[0050] 2. Ensure test consistency and repeatability: All tested SSDs are initialized based on the same "perfect steady state" configuration file, ensuring a high degree of consistency in the test starting point and making the performance data perfectly comparable.
[0051] 3. Significantly reduce testing costs: Reduce equipment downtime and power consumption, and significantly reduce additional wear and tear on SSDs caused by write pre-embedded components, extending the lifespan of testing equipment.
[0052] 4. High flexibility: Different configuration files can be generated for different test scenarios (such as full-disk steady state, half-disk steady state, and steady state with different degrees of fragmentation), enabling rapid switching of test scenarios.
[0053] 5. Easy to integrate and automate: The "one-click steady state" function can be easily integrated into an automated testing framework to achieve a fully automated performance testing pipeline without human intervention.
[0054] Please refer to Figure 9 As a response to the above Figure 1 The implementation of the method shown in this application provides an embodiment of a one-click steady-state testing system for solid-state drives based on configuration import. This system embodiment is similar to... Figure 1 Corresponding to the method embodiments shown, the system can be specifically applied to various electronic devices.
[0055] like Figure 9 As shown, the solid-state drive one-click steady-state testing system based on configuration import in this embodiment includes: a write pre-embedded operation module 51, a steady-state configuration file generation module 52, a solid-state drive reconstruction module 53, and a performance testing module 54, wherein: The write pre-embedded operation module 51 is used to control the reference solid-state drive to perform a write pre-embedded operation until the reference solid-state drive reaches the target test steady state. The steady-state configuration file generation module 52 is used to extract steady-state composition information from the controller of the reference solid-state drive, generate a steady-state configuration file based on the steady-state composition information, and store the steady-state configuration file in the configuration file library; Solid-state drive reconstruction module 53 is used to determine a target steady-state configuration file from the configuration file library and import the target steady-state configuration file into the target solid-state drive under test in the initial state, so that the firmware of the target solid-state drive under test is reconstructed to the target test steady state based on the steady-state configuration file; The performance testing module 54 is used to perform preset performance tests on the reconstructed target solid-state drive and obtain the target test results.
[0056] Furthermore, the steady-state configuration file generation module 52 includes: A steady-state composition information extraction unit is used to extract the steady-state composition information from the controller of the reference solid-state drive through a first NVMe management command or a first manufacturer-defined command. A steady-state composition information encoding unit is used to encode the steady-state composition information into a binary file to generate the steady-state configuration file; A steady-state configuration file storage unit is used to store the steady-state configuration file in the configuration file library.
[0057] The steady-state configuration information is at least one of the following: a logical-to-physical address mapping table, flash memory block status information, garbage collection module status information, and wear leveling module status information.
[0058] Furthermore, the steady-state configuration file storage unit includes: The encryption subunit is used to encrypt and sign the steady-state configuration file to obtain the encrypted steady-state configuration file. The association subunit is used to store the encrypted steady-state configuration file in the configuration file library and associate the encrypted steady-state configuration file with the model, firmware version and test scenario of the benchmark solid-state drive.
[0059] Furthermore, the solid-state drive rebuild module 53 includes: The first erasure unit is used to perform a secure erase operation on the target solid-state drive under test so that the target solid-state drive under test is in its initial state. The file determination unit is used to determine the target steady-state configuration file from the configuration file library in the software interface of the test execution module; The file import unit is used to import the target steady-state configuration file into a specified memory or flash memory area of the controller of the target solid-state drive under test through a second NVMe management command or a second vendor-defined command, so that the firmware of the target solid-state drive under test is rebuilt to the target test steady state based on the steady-state configuration file.
[0060] Furthermore, the document determination unit also includes: The version determination unit is used to determine whether the firmware version of the target steady-state configuration file is consistent with the firmware version of the reference solid-state drive recorded in the configuration file. If they are inconsistent, an error message is returned.
[0061] Furthermore, the performance testing module 54 also includes: The latency detection unit is used to perform a verification write operation on the target solid-state drive under test, detect the write latency of the target solid-state drive under test, and obtain the latency result. The first determination unit is used to determine that steady-state reconstruction is successful if the delay result is within a preset steady-state delay threshold range. The second determination unit is used to determine that the reconstruction has failed and terminate the test process if the delay result is not within the preset steady-state delay threshold range.
[0062] Furthermore, the pre-embedded operation module 51 includes: The second erasure unit is used to perform a secure erase operation on the reference solid-state drive to bring the reference solid-state drive to its initial state. The write pre-embedded operation execution unit is used to control the reference solid-state drive to perform write pre-embedded operations through sequential write pre-embedded operations and random write pre-embedded operations until the reference solid-state drive reaches the target test steady state.
[0063] Obviously, the embodiments described above are merely some embodiments of this application, not all embodiments. The accompanying drawings show preferred embodiments of this application, but do not limit the scope of this application. This application can be implemented in many different forms; rather, these embodiments are provided to provide a more thorough and comprehensive understanding of the disclosure of this application. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing specific embodiments, or make equivalent substitutions for some of the technical features. Any equivalent structures made using the content of this application's specification and drawings, directly or indirectly applied to other related technical fields, are similarly within the scope of protection of this application.
Claims
1. A one-click steady-state testing method for solid-state drives based on configuration import, characterized in that, include: Control the benchmark solid-state drive to perform write pre-embedded operations until the benchmark solid-state drive reaches the target test steady state; Steady-state configuration information is extracted from the controller of the reference solid-state drive, and a steady-state configuration file is generated based on the steady-state configuration information. The steady-state configuration file is then stored in the configuration file library. The target steady-state configuration file is determined from the configuration file library and imported into the target solid-state drive under test in its initial state, so that the firmware of the target solid-state drive under test is rebuilt to the target test steady state based on the steady-state configuration file. The preset performance tests are performed on the reconstructed target solid-state drive to obtain the target test results.
2. The one-click steady-state testing method for solid-state drives based on configuration import as described in claim 1, characterized in that, The step of extracting steady-state configuration information from the controller of the reference solid-state drive, generating a steady-state configuration file based on the steady-state configuration information, and storing the steady-state configuration file in a configuration file library includes: The steady-state configuration information is extracted from the controller of the reference solid-state drive using a first NVMe management command or a first vendor-defined command. The steady-state configuration information is encoded into a binary file to generate the steady-state configuration file. The steady-state configuration file is stored in the configuration file library.
3. The one-click steady-state testing method for solid-state drives based on configuration import as described in claim 2, characterized in that, The steady-state configuration information is at least one of the following: a logical-to-physical address mapping table, flash memory block status information, garbage collection module status information, and wear leveling module status information.
4. The one-click steady-state testing method for solid-state drives based on configuration import as described in claim 2, characterized in that, The step of storing the steady-state configuration file in the configuration file library includes: The steady-state configuration file is encrypted and signed to obtain an encrypted steady-state configuration file; The encrypted steady-state configuration file is stored in the configuration file library, and the encrypted steady-state configuration file is associated with the model, firmware version and test scenario of the benchmark solid-state drive.
5. The one-click steady-state testing method for solid-state drives based on configuration import as described in claim 1, characterized in that, The step of determining the target steady-state configuration file from the configuration file library and importing the target steady-state configuration file into the target solid-state drive under test in its initial state, so that the firmware of the target solid-state drive under test is rebuilt to the target test steady state based on the steady-state configuration file, includes: Perform a secure erase operation on the target solid-state drive under test to bring it to its initial state. In the software interface of the test execution module, the target steady-state configuration file is determined from the configuration file library; The target steady-state configuration file is imported into a designated memory or flash memory area of the controller of the target SSD under test through a second NVMe management command or a second vendor-defined command, so that the firmware of the target SSD under test is rebuilt to the target test steady state based on the steady-state configuration file.
6. The one-click steady-state testing method for solid-state drives based on configuration import as described in claim 5, characterized in that, After determining the target steady-state configuration file from the configuration file library in the software interface of the test execution module, the method further includes: Determine whether the firmware version of the target steady-state configuration file is consistent with the firmware version of the baseline solid-state drive recorded in the configuration file. If they are inconsistent, return an error message.
7. The one-click steady-state testing method for solid-state drives based on configuration import according to any one of claims 1 to 6, characterized in that, Before performing preset performance tests on the reconstructed target solid-state drive and obtaining the target test results, the method further includes: Perform a verification write operation on the target solid-state drive under test, and detect the write latency of the target solid-state drive under test to obtain the latency result; If the delay result is within the preset steady-state delay threshold range, then the steady-state reconstruction is determined to be successful; If the delay result is not within the preset steady-state delay threshold range, the reconstruction is determined to have failed and the test process is terminated.
8. The one-click steady-state testing method for solid-state drives based on configuration import according to any one of claims 1 to 6, characterized in that, The control benchmark solid-state drive performs a write pre-embedding operation until the benchmark solid-state drive reaches the target test steady state, including: Perform a secure erase operation on the reference solid-state drive to bring it to its initial state; The benchmark solid-state drive is controlled to perform write pre-embedding operations by sequential write pre-embedding and random write pre-embedding operations until the benchmark solid-state drive reaches the target test steady state.
9. A one-click steady-state testing system for solid-state drives based on configuration import, characterized in that, include: The write pre-embedded operation module is used to control the reference solid-state drive to perform write pre-embedded operations until the reference solid-state drive reaches the target test steady state; A steady-state configuration file generation module is used to extract steady-state composition information from the controller of the reference solid-state drive, generate a steady-state configuration file based on the steady-state composition information, and store the steady-state configuration file in a configuration file library; The solid-state drive reconstruction module is used to determine the target steady-state configuration file from the configuration file library and import the target steady-state configuration file into the target solid-state drive under test in the initial state, so that the firmware of the target solid-state drive under test is reconstructed to the target test steady state based on the steady-state configuration file; The performance testing module is used to perform preset performance tests on the reconstructed target solid-state drive and obtain the target test results.
10. The one-click steady-state testing system for solid-state drives based on configuration import according to claim 9, characterized in that, The steady-state configuration file generation module includes: A steady-state composition information extraction unit is used to extract the steady-state composition information from the controller of the reference solid-state drive through a first NVMe management command or a first manufacturer-defined command. A steady-state composition information encoding unit is used to encode the steady-state composition information into a binary file to generate the steady-state configuration file; A steady-state configuration file storage unit is used to store the steady-state configuration file in the configuration file library.