> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/references/database-information-and-organization/user-input-delay.md).
# User input delay
Determining performance degradations based solely on standard system health metrics like CPU, memory, and disk input or output is a difficult task. For example, on virtual desktops, the standard metrics do not often correlate with perceived performance.
The Nexthink solution measures the responsiveness of a Windows session by monitoring the user input delay per session, a Windows performance counter. That counter measures how long any user input using a mouse or a keyboard waits before a process picks it. That value is available for local and remote sessions.
### Configuration
By default, Collector reports the user input delay values as part of the user activity metrics. You can stop monitoring that by disabling the user activity reporting. Find the procedure on the [Configuring Collector level anonymization](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/configuring-collector-level-anonymization.md) page.
### Supported operating systems
All supported Windows versions:
* Windows 11
* Windows Server 2022
### NQL example
```
devices during past 24h
| with session.events
| compute
medium_ratio = duration_with_medium_user_input_delay.sum()/user_interaction_time.sum(),
high_ratio = duration_with_high_user_input_delay.sum() / user_interaction_time.sum()
| where medium_ratio > 0.10 or high_ratio > 0.05
| list device.name, medium_ratio, high_ratio
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.nexthink.com/platform/references/database-information-and-organization/user-input-delay.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.