Не понял, как читать отчёт программы - она же не делит его по временным интервалам. За минуту мониторинга дважды был продолжительный лаг клавиатуры, но в логе только общие данные.
Вывод программа сделала, что всё ок:
"Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:01:00 (h:mm:ss) on all processors."
В остальном такой большой разброс времени выполнения возможно и есть мой лаг, но не знаю, какое там время должно быть по умолчанию.
СПОЙЛЕР »
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.
Highest measured interrupt to process latency (µs): 427,60
Average measured interrupt to process latency (µs): 5,129597
Highest measured interrupt to DPC latency (µs): 425,90
Average measured interrupt to DPC latency (µs): 2,311593
_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
Highest ISR routine execution time (µs): 365,906511
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,007972
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,012275
ISR count (execution time <250 µs): 15348
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 2
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
Highest DPC routine execution time (µs): 313,020367
Driver with highest DPC routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Highest reported total DPC routine time (%): 0,003819
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 536.99 , NVIDIA Corporation
Total time spent in DPCs (%) 0,010738
DPC count (execution time <250 µs): 39518
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 1
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.
NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
Process with highest pagefault count: msmpeng.exe
Total number of hard pagefaults 157
Hard pagefault count of hardest hit process: 88
Number of processes hit: 9