|Non-Confidential||PDF version||ARM 100052_0001_00_en|
|Home > Performance Optimization and Monitoring > RN-I performance events > Bottleneck analysis at RN-I bridges|
The CCN-502 provides events that observe the locations where the nodes or bridges are full, which can cause delays in the rest of the system.
This enables you to monitor the current bottlenecks in the system, and checks multiple events in the RN-Is, HN-Fs, and memory controllers. In the RN-I bridges, the events monitor the following:
The number of times the bridge is forced to retry because of the lack of dynamic credits.
The number of times the read and write tracker is full and therefore cannot accept new requests in the system. This can cause delays in the AXI masters.
The number of read request replays, because of decoupling of the read request buffers and read data buffers in the RN-I system.
TXREQFLITV_RETRIED monitors the efficiency of using dynamic credits in the system.
It does this by measuring the request retry rate:
|TXREQFLITV_RETRIED||Number of retried TXREQ flits dispatched. This event is a measure of the retry rate.|
Calculate the request retry rate as follows:
To monitor the delays for both reads and writes, the CCN-502 enables you to monitor how full the read and write trackers are in the RN-I bridges.
When one of the trackers is full, the bridge cannot accept new requests from the AXI master. This delays the I/O devices that connect to the AXI master.
You can use the measure of how full the trackers are, together with the read and write bandwidth from the RN-I bridge to the interconnect, to help isolate the source of bottlenecks in the system. For example:
You can also use the measure of how full the trackers are with AXI PMUs to monitor delays to the AXI masters.
The following events monitor the read and write trackers:
|RRTFull||All entries in the read request tracker, excluding those reserved for Hi-QPC, are occupied. This is a measure of oversubscription in the read request tracker.|
|WRTFull||All entries in the write request tracker, excluding those reserved for Hi-QPC, are occupied. This is a measure of oversubscription in the write request tracker.|