This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
realtime:documentation:howto:debugging:debug-steps [2018/08/21 13:16] ebugden [Identify the cause] Update link |
realtime:documentation:howto:debugging:debug-steps [2023/10/03 05:39] (current) costa.shul Latency detection tools |
||
---|---|---|---|
Line 64: | Line 64: | ||
After applying the supposed fix, test the system in the original conditions that caused the latency. If the latency does not occur, then this confirms that the latency has been fixed, or at least that it does not occur under those conditions as frequently. However, if the latency is still observed, then it could mean that the problem was correctly identified but that the solution is wrong. It could also mean that a different latency was resolved because the tracing overhead changed the behavior of the system. | After applying the supposed fix, test the system in the original conditions that caused the latency. If the latency does not occur, then this confirms that the latency has been fixed, or at least that it does not occur under those conditions as frequently. However, if the latency is still observed, then it could mean that the problem was correctly identified but that the solution is wrong. It could also mean that a different latency was resolved because the tracing overhead changed the behavior of the system. | ||
+ | |||
+ | |||
+ | More information | ||
+ | * [[realtime:documentation:howto:tools:start#latency_detection|Latency detection tools]] |