-
-
Save renatoruk/55d92204b387549ad313caff6caf9ee0 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| _________________________________________________________________________________________________________ | |
| CONCLUSION | |
| _________________________________________________________________________________________________________ | |
| Your system appears to be suitable for handling real-time audio and other tasks without dropouts. | |
| LatencyMon has been analyzing your system for 0:03:56 (h:mm:ss) on all processors. | |
| _________________________________________________________________________________________________________ | |
| SYSTEM INFORMATION | |
| _________________________________________________________________________________________________________ | |
| Computer name: mycomputer | |
| OS version: Windows 10, 10.0, version 1909, build: 18363 (x64) | |
| Hardware: Z270-HD3P, Gigabyte Technology Co., Ltd. | |
| CPU: GenuineIntel Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz | |
| Logical processors: 8 | |
| Processor groups: 1 | |
| RAM: 16296 MB total | |
| _________________________________________________________________________________________________________ | |
| CPU SPEED | |
| _________________________________________________________________________________________________________ | |
| Reported CPU speed: 420 MHz | |
| Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results. | |
| _________________________________________________________________________________________________________ | |
| 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): 359,40 | |
| Average measured interrupt to process latency (µs): 5,592411 | |
| Highest measured interrupt to DPC latency (µs): 349,80 | |
| Average measured interrupt to DPC latency (µs): 2,145748 | |
| _________________________________________________________________________________________________________ | |
| 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): 31,566190 | |
| Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation | |
| Highest reported total ISR routine time (%): 0,007726 | |
| Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation | |
| Total time spent in ISRs (%) 0,009192 | |
| ISR count (execution time <250 µs): 108871 | |
| ISR count (execution time 250-500 µs): 0 | |
| ISR count (execution time 500-1000 µs): 0 | |
| 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): 347,833333 | |
| Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation | |
| Highest reported total DPC routine time (%): 0,273559 | |
| Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation | |
| Total time spent in DPCs (%) 0,388305 | |
| DPC count (execution time <250 µs): 775370 | |
| DPC count (execution time 250-500 µs): 0 | |
| DPC count (execution time 500-10000 µs): 24 | |
| 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: svchost.exe | |
| Total number of hard pagefaults 11 | |
| Hard pagefault count of hardest hit process: 6 | |
| Number of processes hit: 2 | |
| _________________________________________________________________________________________________________ | |
| PER CPU DATA | |
| _________________________________________________________________________________________________________ | |
| CPU 0 Interrupt cycle time (s): 12,178325 | |
| CPU 0 ISR highest execution time (µs): 31,566190 | |
| CPU 0 ISR total execution time (s): 0,173630 | |
| CPU 0 ISR count: 108871 | |
| CPU 0 DPC highest execution time (µs): 347,833333 | |
| CPU 0 DPC total execution time (s): 7,278914 | |
| CPU 0 DPC count: 767733 | |
| _________________________________________________________________________________________________________ | |
| CPU 1 Interrupt cycle time (s): 1,960650 | |
| CPU 1 ISR highest execution time (µs): 0,0 | |
| CPU 1 ISR total execution time (s): 0,0 | |
| CPU 1 ISR count: 0 | |
| CPU 1 DPC highest execution time (µs): 197,005238 | |
| CPU 1 DPC total execution time (s): 0,017291 | |
| CPU 1 DPC count: 934 | |
| _________________________________________________________________________________________________________ | |
| CPU 2 Interrupt cycle time (s): 1,874567 | |
| CPU 2 ISR highest execution time (µs): 0,0 | |
| CPU 2 ISR total execution time (s): 0,0 | |
| CPU 2 ISR count: 0 | |
| CPU 2 DPC highest execution time (µs): 54,570952 | |
| CPU 2 DPC total execution time (s): 0,018819 | |
| CPU 2 DPC count: 3322 | |
| _________________________________________________________________________________________________________ | |
| CPU 3 Interrupt cycle time (s): 1,759747 | |
| CPU 3 ISR highest execution time (µs): 0,0 | |
| CPU 3 ISR total execution time (s): 0,0 | |
| CPU 3 ISR count: 0 | |
| CPU 3 DPC highest execution time (µs): 41,076667 | |
| CPU 3 DPC total execution time (s): 0,001156 | |
| CPU 3 DPC count: 340 | |
| _________________________________________________________________________________________________________ | |
| CPU 4 Interrupt cycle time (s): 1,874793 | |
| CPU 4 ISR highest execution time (µs): 0,0 | |
| CPU 4 ISR total execution time (s): 0,0 | |
| CPU 4 ISR count: 0 | |
| CPU 4 DPC highest execution time (µs): 50,254762 | |
| CPU 4 DPC total execution time (s): 0,005641 | |
| CPU 4 DPC count: 1130 | |
| _________________________________________________________________________________________________________ | |
| CPU 5 Interrupt cycle time (s): 1,583192 | |
| CPU 5 ISR highest execution time (µs): 0,0 | |
| CPU 5 ISR total execution time (s): 0,0 | |
| CPU 5 ISR count: 0 | |
| CPU 5 DPC highest execution time (µs): 62,954524 | |
| CPU 5 DPC total execution time (s): 0,002256 | |
| CPU 5 DPC count: 340 | |
| _________________________________________________________________________________________________________ | |
| CPU 6 Interrupt cycle time (s): 1,837203 | |
| CPU 6 ISR highest execution time (µs): 0,0 | |
| CPU 6 ISR total execution time (s): 0,0 | |
| CPU 6 ISR count: 0 | |
| CPU 6 DPC highest execution time (µs): 40,419524 | |
| CPU 6 DPC total execution time (s): 0,006030 | |
| CPU 6 DPC count: 969 | |
| _________________________________________________________________________________________________________ | |
| CPU 7 Interrupt cycle time (s): 1,770805 | |
| CPU 7 ISR highest execution time (µs): 0,0 | |
| CPU 7 ISR total execution time (s): 0,0 | |
| CPU 7 ISR count: 0 | |
| CPU 7 DPC highest execution time (µs): 61,313571 | |
| CPU 7 DPC total execution time (s): 0,004485 | |
| CPU 7 DPC count: 626 | |
| _________________________________________________________________________________________________________ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment