Tackling Peak User Input Delay (secs) with ControlUp

Trentent gave advice seeking to identify why application performance on physical machines had a peak user input delay up to 15 seconds – the default trigger priority boost for processes has a threshold of 300ms. Edge DX was installed and CPU spikes were not observed. It was fixed in the Beta 2 for Windows and can be due to any number of causes such as latency with proxies and disk issues. User input delay can be inspected with the newest agent.

Read the entire ‘Tackling Peak User Input Delay (secs)’ thread below:

Taking a dive in to this metric: Peak User Input Delay (secs)

Its not one I am too familiar with. In this case, I’m investigating app performance on physical machines. Is there any number of sec where this should be concerning? I’m seeing peaks to 15 sec.

Trentent is schooling me from the past: 😉https://www.youtube.com/watch?v=6ZrOeBVV4qw

We have a default trigger that raises the priority of a process when input delay reaches more than 300ms, so yes, 15 seconds before the app responds to your keyboard click is A LOT 😁

I only have Edge DX installed. and I’m struggling to see what app may be causing this.

and the delay spikes are not tied to any CPU Spikes

Check the stopped processes data index

Per process user input delay was broken and is now fixed in the Beta 2 for Windows

And the fact that there is no CPU spikes is the beauty of this counter: it can be any thing 🙂

From the latency with the proxy to the disk at max capacities…

I’d recommend to upgrade the version of your agent and start investigate the processes suffereing from high user input delay

depending on the process, you should be able to trigger the right troubleshooting process

I’m on the newest agent.

Continue reading and comment on the thread ‘Tackling Peak User Input Delay (secs) with ControlUp’.  Not a member? Join Here!