> This feature is very useful to analyze specific delay sources due to memory operations. > > But these shown datas are basically average values rather than min/max, it's not enough > > for debugging delay jitters. Will you add showing min/max values to delaytop in future? Hi Xu, Thanks for the review and the great suggestions! You’re right, averages alone aren’t enough for diagnosing the sources of delay jitter. I will work on adding min/max support in the next version. > I think if users press 'M', delaytop doesn't need to shown CPU/IRQ/IO delays, just show the detailed memory delays. Good point. When ‘M’ is pressed, the user wants to focus on memory. Showing CPU/IRQ/IO is just noise. I’ll change the behavior in the next version so that ‘M’ switches to a clean, memory-only view. Best regards, Fan Yu
