A performance analysis method and system of a tracking system, a terminal and a storage medium

Abstract

The present application relates to the technical field of data processing, and especially relates to a performance analysis method and system of a tracking system, a terminal and a storage medium. The method comprises the following steps: obtaining an information table, processing the information table and generating a corresponding unpacker and analyzer; the unpacker is connected with input and output signals of a system tracking unit, the analyzer is connected with internal signals of the system tracking unit and the unpacker and sends an excitation; the unpacker unpacks tracking data and tracking flow; the analyzer collects a system tracking unit verification environment and an analyzer specified output file address and an output mode; whether information of tracking protocol content and data content is consistent with information of a tracking data packet type and a tracking data packet content is judged; if not, it is determined that the tracking data is discarded or delayed, and comparison information content is recorded. The present application automatically generates an unpacker and an analyzer through a single table file, and reduces the effort and time required for analyzing the performance of the system tracking.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a performance analysis method, system, terminal, and storage medium for a tracking system. Background Technology

[0002] As an effective means of on-chip debugging, tracing systems have always been a key focus in on-chip system design. In recent years, with the development of chip technology, the design details and specifications of tracing systems in different on-chip systems have become increasingly different. To unify these designs and protocols, one of the most common solutions on the market is to use a unified tracing protocol to package tracing data from tracing sources with different designs and specifications. In a typical tracing system, a dedicated module is often used to perform this function. After packaging the tracing data into a unified protocol, it is sent to external devices for analysis or temporarily stored on-chip through a unified data path, thereby improving the accuracy of tracing data transmission. We call this module the system tracing unit. Due to the nature of the system tracing unit's operation, multiple tracing sources, and even the entire tracing system's tracing sources, converge here. Therefore, many performance bottlenecks and blockages occur here, and the performance of different tracing systems in different application scenarios has become a topic of concern.

[0003] In different tracking systems, the data sent by the tracking source can vary significantly. If the tracking source sends tracking data too quickly or in too large a volume, and the system tracking unit cannot keep up with the packetization, the system tracking unit will choose to discard or pause receiving tracking data based on the user's configuration to ensure the accuracy of data transmission. Furthermore, due to bandwidth limitations, after discarding or pausing, the system tracking unit can often only provide the user with brief information as a reminder; more detailed information will not be collected or sent. In practical applications, this information is crucial for performance optimization and improving tracking bandwidth. Testers often need to spend considerable effort capturing data from the tracking source and system tracking unit outputs one by one through boundary signals and performing complex comparisons to obtain this information. After obtaining the data, they still need to compare and analyze this massive amount of data, making it difficult to quickly grasp key information and performance indicators, resulting in low efficiency. Summary of the Invention

[0004] To address the technical problems in the existing technology, where testers often have to spend a lot of time capturing data from the tracking source and system tracking unit outputs one by one through boundary signals and performing complex comparisons, and then comparing and analyzing this massive amount of data, making it difficult to quickly grasp key information and performance indicators, resulting in low efficiency, this invention provides a performance analysis method for tracking systems to quickly grasp key information and performance indicators and improve processing efficiency.

[0005] To address the aforementioned issues, this invention patent develops a performance analysis tool for commonly used system tracing units in tracing systems. This invention primarily improves upon traditional testing methods in terms of process and methodology. It provides a depacker to unpack the tracing data input to the system tracing unit, converting it into user-understandable data containing tracing protocol information according to the packaging protocol, and outputting it to a dedicated file or printing it out in real-time during operation. This depacker also unpacks the output of the system tracing unit, converting its output tracing stream into a user-friendly format. The unpacked information is collected by an analyzer to analyze the tracing performance of the system tracing unit, including marking discarded tracing data, the waiting time for marked pending tracing data, and key performance indicators from different tracing sources.

[0006] The unpackers and analyzers mentioned above can be automatically generated by scripts by modifying a single table file, and then reused in all tracing systems that use system tracing units. This approach can reduce the significant time spent writing tools and performing performance analysis for different tracing systems under test, and also facilitates inheritance in subsequent projects, making management and maintenance easier.

[0007] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0008] An information table is obtained, which includes parameters defining the current system tracking unit integration method. The information table is processed to generate corresponding unpackers and analyzers. The unpacker is connected to the input and output signals of the system tracking unit, and the analyzer is connected to the internal signals of the system tracking unit and the unpacker, and sends stimuli. Corresponding tracking data and tracking streams are obtained from the tracking source and the system tracking unit, respectively. The unpacker unpacks the tracking data and tracking streams, respectively, into tracking protocol content and data content information, tracking data packet type and tracking data packet content information, and sends them to the analyzer after attaching the simulation time. The analyzer collects the system tracking unit verification environment and the analyzer-specified output file address, as well as the output mode. It judges whether the tracking protocol content and data content information are consistent with the tracking data packet type and tracking data packet content information. If they are consistent, it is determined that the data packet was not discarded or delayed; if not, it is determined that the data packet was discarded or delayed, and the comparison information content is recorded.

[0009] As a further aspect of the present invention, the parameters of the current system tracking unit integration method include one or more combinations of protocol format, FIFO depth, timestamp length, and data bit width.

[0010] As a further aspect of the present invention, the information table is formatted as CSV.

[0011] As a further aspect of the present invention, the tracking protocol content includes tracking data packet type and ID.

[0012] As a further aspect of the present invention, the system tracking unit verifies the environment including the FIFO capacity, occupancy rate, and flags indicating data discard or waiting.

[0013] As a further aspect of the present invention, the comparative information includes specific tracking data and delay period of erroneous packet dropping; it also records the data of FIFO occupancy changing with simulation time, and analyzes different tracking data and tracking streams to output waiting ratio and dropping ratio information of tracking data from different tracking sources.

[0014] As a further aspect of the present invention, the analyzer outputs modes including a simplified mode and a full mode.

[0015] As a further embodiment of the present invention, in the simplified mode, the analyzer will omit the continuously repeated MID and CID in the unpacked data of the tracking data, and output them again in the log when they change, in accordance with the tracking stream format output by the system tracking unit. At the same time, the synchronization packet and verification packet in the unpacked tracking stream data output by the system tracking unit will be ignored.

[0016] After connecting and configuring the unpacker and analyzer, the user starts the tracing system, inputs tracing data into the system tracing unit through the tracing source, and then finds the required analyzer logs in the defined output file to analyze the performance of the system tracing unit.

[0017] Secondly, in another embodiment provided by the present invention, a performance analysis system for a tracking system is provided, the performance analysis system for a tracking system including a table information acquisition module, a connection stimulus module and a judgment analysis module;

[0018] The table information acquisition module is used to acquire an information table, which includes parameters used to define the current system tracking unit integration method;

[0019] The unpacker and analyzer generation module is used to process the information table and generate the corresponding unpacker and analyzer;

[0020] The connection excitation module is used to connect the unpacker to the input and output signals of the system tracking unit, and the analyzer is connected to the internal signals of the system tracking unit and the unpacker to send excitations;

[0021] The unpacker is used to obtain the corresponding tracking data and tracking stream from the tracking source and the system tracking unit, respectively. The unpacker unpacks the tracking data and tracking stream into tracking protocol content and data content information, tracking data packet type and tracking data packet content information, and sends them to the analyzer after attaching the simulation time. The analyzer is used to collect the system tracking unit verification environment and the output file address specified by the analyzer, as well as the output mode.

[0022] The judgment and analysis module determines whether the information of the tracking protocol content and data content is consistent with the information of the tracking data packet type and tracking data packet content. If they are consistent, it is determined that the data packet was not dropped or was delayed; if not, it is determined that the data packet was dropped or was delayed, and the comparison information is recorded.

[0023] Thirdly, in another embodiment provided by the present invention, a terminal is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor loads and executes the computer program to implement the steps of a performance analysis method for a tracking system.

[0024] Fourthly, in another embodiment of the present invention, a storage medium is provided storing a computer program that, when loaded and executed by a processor, implements the steps of the performance analysis method of the tracking system.

[0025] The technical solution provided by this invention has the following beneficial effects: This patent proposes an automated solution to common problems of system tracking units in tracking systems. By automatically generating unpackers and analyzers from a single table file, the effort and time required for tracking performance analysis of this system are reduced.

[0026] This invention provides a solution for quickly identifying and locating functional errors or performance problems in system tracing units through unpackers and analyzers generated by automated scripts. For users who haven't yet created exciters, this invention also provides automatically generated exciters so users can input their desired exciters and quickly complete verification. Finally, this invention has strong extensibility and reusability; all components are automatically generated through scripts, and users can modify the configuration files according to parameter definitions to generate analyzers and unpackers that meet their needs, greatly saving time in developing the verification environment. The application of templates makes the test case structure more reasonable and standardized.

[0027] Both the unpacker and the analyzer can be automatically generated by scripts by modifying a single table file, and then reused in all tracing systems that use system tracing units. This approach can reduce the significant time spent writing tools and performing performance analysis for different tracing systems under test, and also facilitates inheritance in subsequent projects, making management and maintenance easier.

[0028] These or other aspects of the invention will become more apparent from the following description of embodiments. It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the invention.

[0029] These or other aspects of the invention will become more apparent from the following description of embodiments. It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the invention. Attached Figure Description

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

[0031] Figure 1 This is a structural diagram of the system tracking unit verification system in a performance analysis method for a tracking system according to an embodiment of the present invention;

[0032] Figure 2 This is a flowchart illustrating the system tracking unit verification process in a performance analysis method for a tracking system according to an embodiment of the present invention.

[0033] Figure 3 This is a structural block diagram of a performance analysis system for a tracking system according to an embodiment of the present invention. Detailed Implementation

[0034] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0035] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it necessarily have to be performed in the order described. For example, some operations / steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0036] It should be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0037] Specifically, the embodiments of the present invention will be further described below with reference to the accompanying drawings.

[0038] Please see Figure 1 Currently, the most widely used system tracing unit is based on the Arm-based STP tracing protocol. It receives tracing data from other tracing sources via the AXI interface, determines the attributes of the tracing data after it is packaged according to the tracing protocol based on the address mapping of the AXI interface, packages it according to the tracing protocol, and then sends it to other components of the tracing system for further routing via the ATB interface. The following implementation will also use this system tracing unit as an example.

[0039] The user connects the unpacker to the input and output interfaces of the system tracing unit, enabling it to receive input tracing data and output tracing streams from the system tracing unit. The user then connects some signals within the analyzer, unpacker, and system tracing unit. After starting the system under test, the tracing source sends tracing data to the tracing unit. The user can then perform performance analysis by viewing the logs output by the analyzer. See details... Figure 1 .

[0040] The main focus of this invention is to determine whether each tracking data sent from a tracking source to the system tracking unit has been successfully transmitted or discarded, and to analyze the performance of the system tracking unit. The unpacker and analyzer designed for this purpose can obtain this information by processing and analyzing the input and output data of the system tracking unit, thereby improving the reliability of verification.

[0041] The steps for generating and integrating unpackers and analyzers, and their operation in front-end verification, are as follows: Figure 2 As shown.

[0042] In this embodiment; 1. Define a table file: This invention specifies a series of entries to describe the information of the system tracing unit currently under test. In actual use, this information is initially defined according to requirements during integration, and then this information can be filled into the table. For example, the system tracing units to be analyzed are as shown in Table 1:

[0043]

[0044] Table 1 System Tracking Unit Definition Table File

[0045] As shown in Table 1, the tracking unit of this system contains a data FIFO with a depth of 32 and a channel ID FIFO with a depth of 8. It does not integrate a hardware event observation interface, has an AXIID of 8, uses the STPv2 protocol, records a complete timestamp, supports a maximum data size of 32 bits, and supports both Invarianttiming and Guaranteed transmission (also known as discard and pause as mentioned above).

[0046] 2. Automatic Generation of Unpackers and Analyzers: The system automatically reads a spreadsheet file and generates different unpackers and analyzers based on predefined templates. These steps are all automated, requiring no manual intervention. However, users still need to connect the generated unpackers and analyzers to the corresponding verification environment. The automated tool can be implemented using any scripting language. It first reads and analyzes the predefined spreadsheet file, then generates unpackers and analyzers based on the parameters in the spreadsheet file, and finally generates corresponding files for easy integration into the verification environment.

[0047] 3. Connect the unpacker and analyzer and send stimuli: After the unpacker and analyzer are generated, the user needs to connect them to the current verification environment. The unpacker needs to be connected to the input and output signals of the system tracing unit, and the analyzer needs to be connected to certain internal signals of the system tracing unit as well as the unpacker. The files for the unpacker and analyzer also need to be included in the verification environment and compiled. In addition, the user needs to specify the output file address for the analyzer, as well as the output mode—abbreviated mode or full mode.

[0048] In simplified mode, the analyzer omits consecutively repeated MIDs and CIDs in the unpacked trace data, only outputting them again in the log when they change. This further aligns the data with the trace stream format output by the system tracing unit, facilitating data location for users. It also ignores meaningless data packets such as synchronization and checksum packets in the unpacked trace stream data output by the system tracing unit, improving readability.

[0049] After connecting and configuring the unpacker and analyzer, the user can start the tracing system, input tracing data into the system tracing unit through the tracing source, and then find the required analyzer logs in the defined output file to further analyze the performance of the system tracing unit.

[0050] In addition to printing logs to a specific file, the analyzer also supports printing relevant log information in real time during test case execution using formats such as uvm_info. To avoid excessive clutter, users can also disable this feature.

[0051] In practical applications, larger and more complex tracking systems often integrate multiple different system tracking units, and the tracking sources may be located in different places and have undergone multiple routes. For such complex scenarios, users can also generate multiple sets of different unpackers and analyzers, and integrate them on each system tracking unit node and tracking source where performance needs to be monitored, thereby obtaining more detailed performance data and assisting users in performing more complex and efficient analyses.

[0052] Here are some examples of analyzer integration and analyzer logging:

[0053]

[0054]

[0055] 4. Analyze the functionality and performance of the system tracing unit based on the analyzer logs: By checking the logs and using the information provided by the analyzer, the blocking status and load of the system tracing unit in the current tracing system can be quickly and clearly determined, which can help users further optimize the tracing system or adjust the integrated parameters of the system tracing unit.

[0056] As shown in the TraceSource column of the analyzer log above, we can see that the trace source with MID 0x5 and CID 0x3 sent I_D32 type trace data at 10000ns and sent G_D32M type data at 20000ns waited for 13 cycles before being received by the system trace unit.

[0057] From the TraceOutput column, we can see that in order to send this G_D32M type data, the system tracing unit used the synchronization packets ASYNC and VERSION, and sent the corresponding MID and CID of this data through M8 and C8 packets respectively, and finally sent the D32M packet.

[0058] The bottom two lines analyze the FIFO utilization of the system tracing unit. It can be seen that the FIFO occupancy rate of the system tracing unit is only 43% by time, but the overflow time accounts for 51%.

[0059] A simple analysis of this sample log reveals that a certain tracing source is consuming a significant portion of the system tracing unit's load, resulting in substantial data loss or excessively long waiting times for its data. From this perspective, we need to optimize the frequency of this tracing source's log transmissions, avoiding excessive concentration or rapid transmission that could overwhelm the tracing system's bandwidth. Furthermore, performance analysis of the system tracing unit's FIFO shows low utilization, with a significant gap between high and low loads. The FIFO is in an overflow state for a considerable period, necessitating optimization of data transmission arbitration and peak values ​​to prioritize log transmissions rather than concentrating them within a single timeframe.

[0060] Besides performance analysis, users can also quickly and clearly identify functional errors based on the data obtained from unpacking. This can be done simply by comparing the data with the user-defined incentives and corresponding protocols; further details are omitted here.

[0061] In one embodiment, see Figure 3 As shown, an embodiment of the present invention also provides a performance analysis system for a tracking system, which includes a table information acquisition module, a connection stimulus module, and a judgment and analysis module.

[0062] The table information acquisition module is used to acquire an information table, which includes parameters used to define the current system tracking unit integration method;

[0063] The unpacker and analyzer generation module is used to process the information table and generate the corresponding unpacker and analyzer;

[0064] The connection excitation module is used to connect the unpacker to the input and output signals of the system tracking unit, and the analyzer is connected to the internal signals of the system tracking unit and the unpacker to send excitations;

[0065] The unpacker is used to obtain the corresponding tracking data and tracking stream from the tracking source and the system tracking unit, respectively. The unpacker unpacks the tracking data and tracking stream into tracking protocol content and data content information, tracking data packet type and tracking data packet content information, and sends them to the analyzer after attaching the simulation time.

[0066] The analyzer is used to verify the environment and output file address specified by the analyzer from the collection system trace unit, as well as the output mode;

[0067] The judgment and analysis module determines whether the information of the tracking protocol content and data content is consistent with the information of the tracking data packet type and tracking data packet content. If they are consistent, it is determined that the data packet was not dropped or was delayed; if not, it is determined that the data packet was dropped or was delayed, and the comparison information is recorded.

[0068] In one embodiment, the present invention also provides a terminal, including a processor AA1, a communication interface AA2, a memory AA3, and a communication bus AA4, wherein the processor AA1, the communication interface AA2, and the memory AA3 communicate with each other through the communication bus AA4.

[0069] Memory AA3 is used to store computer programs;

[0070] When processor AA1 executes the computer program stored in memory AA3, it performs the performance analysis method of the aforementioned tracking system. When executing instructions, the processor implements the steps described in the above method embodiment:

[0071] The communication bus mentioned in the above terminal can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0072] The communication interface is used for communication between the aforementioned terminal and other devices.

[0073] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0074] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0075] The terminal includes user equipment and network equipment. The user equipment includes, but is not limited to, computers, smartphones, and PDAs. The network equipment includes, but is not limited to, a single network server, a server group consisting of multiple network servers, or a cloud based on cloud computing, which is a type of distributed computing consisting of a super virtual computer composed of a group of loosely coupled computers. The terminal can operate independently to implement this invention, or it can connect to a network and interact with other terminals on the network to implement this invention. The network in which the terminal is located includes, but is not limited to, the Internet, wide area network (WAN), metropolitan area network (MAN), local area network (LAN), and VPN network.

[0076] The terminal includes user equipment and network equipment. The user equipment includes, but is not limited to, computers, smartphones, and PDAs. The network equipment includes, but is not limited to, a single network server, a server group consisting of multiple network servers, or a cloud based on cloud computing, which is a type of distributed computing consisting of a super virtual computer composed of a group of loosely coupled computers. The terminal can operate independently to implement this invention, or it can connect to a network and interact with other terminals on the network to implement this invention. The network in which the terminal is located includes, but is not limited to, the Internet, wide area network (WAN), metropolitan area network (MAN), local area network (LAN), and VPN network.

[0077] It should also be understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0078] In one embodiment of the present invention, a storage medium is also provided, on which a computer program is stored, which, when executed by a processor, implements the steps in the above method embodiments:

[0079] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Furthermore, any references to memory, storage, databases, or other media used in the embodiments provided by this invention can include at least one of non-volatile and volatile memory.

[0080] It should be understood that, as used herein, the singular form "a" is intended to include the plural form as well, unless the context clearly supports an exception. It should also be understood that, as used herein, "and / or" refers to any and all possible combinations of one or more of the associatedly listed items. The embodiment numbers disclosed above are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0081] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of the invention (including the claims) is limited to these examples. Within the framework of the invention, technical features of the above embodiments or different embodiments can be combined, and many other variations of different aspects of the invention exist, which are not provided in the details for the sake of brevity. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the invention should be included within the protection scope of the invention.

Claims

1. A performance analysis method for a tracking system, characterized in that, The method includes: acquiring an information table, which includes parameters defining the current system tracking unit integration method; processing the information table to generate a corresponding unpacker and analyzer; connecting the unpacker to the input and output signals of the system tracking unit, and connecting the analyzer to the internal signals of the system tracking unit and the unpacker to send stimuli; acquiring corresponding tracking data and tracking streams from the tracking source and the system tracking unit respectively; unpacking the tracking data and tracking streams into tracking protocol content and data content information, tracking data packet type and tracking data packet content information, and sending them to the analyzer after attaching the simulation time; the analyzer collecting the system tracking unit verification environment and the analyzer-specified output file address, as well as the output mode; determining whether the tracking protocol content and data content information are consistent with the tracking data packet type and tracking data packet content information; if they are consistent, determining that the data packet was not discarded or delayed; if not, determining that the data packet was discarded or delayed, and recording the comparison information content. The comparison information includes specific tracking data and delay periods for dropped error packets; it also records the FIFO occupancy data as the simulation time changes, analyzes different tracking data and tracking streams, and outputs waiting ratio and drop ratio information for tracking data from different tracking sources. The analyzer outputs a simplified mode, which includes: the analyzer omitting consecutively repeated MIDs and CIDs in the unpacked trace data, only outputting them again in the log when they change, and ignoring meaningless data packets, including synchronization packets and check packets, in the unpacked trace stream data output by the system trace unit.

2. The performance analysis method for a tracking system as described in claim 1, characterized in that, The parameters of the current system tracking unit integration method include one or more combinations of protocol format, FIFO depth, timestamp length, and data bit width.

3. The performance analysis method for a tracking system as described in claim 1, characterized in that, The information table is in CSV format.

4. The performance analysis method for a tracking system as described in claim 1, characterized in that, The tracking protocol includes the tracking data packet type and ID.

5. The performance analysis method for a tracking system as described in claim 1, characterized in that, The system tracking unit verifies the environment, including the FIFO capacity, occupancy rate, and flags indicating data discard or waiting.

6. The performance analysis method for a tracking system as described in claim 1, characterized in that, The analyzer outputs a full mode.

7. A performance analysis system for a tracking system, characterized in that, The performance analysis system of the tracking system includes a table information acquisition module, a connection incentive module, and a judgment and analysis module; A table information acquisition module is used to acquire an information table, which includes parameters used to define the current system tracking unit integration method; The unpacker and analyzer generation module is used to process the information table and generate the corresponding unpacker and analyzer; The connection excitation module is used to connect the unpacker to the input and output signals of the system tracking unit, and the analyzer is connected to the internal signals of the system tracking unit and the unpacker to send excitations; The unpacker is used to obtain the corresponding tracking data and tracking stream from the tracking source and the system tracking unit, respectively. The unpacker unpacks the tracking data and tracking stream into tracking protocol content and data content information, tracking data packet type and tracking data packet content information, and sends them to the analyzer after attaching the simulation time. The analyzer is used to collect the system tracking unit verification environment and the output file address specified by the analyzer, as well as the output mode. The judgment and analysis module is used to determine whether the information of the tracking protocol content and data content is consistent with the information of the tracking data packet type and tracking data packet content. If they are consistent, it is determined that the data packet was not dropped or was delayed; if not, it is determined that the data packet was dropped or was delayed, and the comparison information is recorded. The comparison information includes specific tracking data and delay periods for dropped error packets; it also records the FIFO occupancy data as the simulation time changes, analyzes different tracking data and tracking streams, and outputs waiting ratio and drop ratio information for tracking data from different tracking sources. The analyzer outputs a simplified mode, which includes: the analyzer omitting consecutively repeated MIDs and CIDs in the unpacked trace data, only outputting them again in the log when they change, and ignoring meaningless data packets, including synchronization packets and check packets, in the unpacked trace stream data output by the system trace unit.

8. A terminal comprising a memory and a processor, the memory storing a computer program, the processor loading and executing the computer program to implement the steps of the performance analysis method for the tracking system as claimed in any one of claims 1-6.

9. A storage medium storing a computer program, which, when loaded and executed by a processor, implements the steps of the performance analysis method for the tracking system as described in any one of claims 1-6.

Images