help me ! latency is killing me !
- 1 réponse
- 2 participants
- 955 vues
- 2 followers
Houssem Hmida
1
Nouvel·le AFfilié·e
Membre depuis 7 ans
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 1:26:59 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: FC-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: LIFEBOOK AH530, FUJITSU, FJNBB06
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz
Logical processors: 4
Processor groups: 1
RAM: 3892 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2394 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): 1055723,059695
Average measured interrupt to process latency (µs): 7,094048
Highest measured interrupt to DPC latency (µs): 1055668,737882
Average measured interrupt to DPC latency (µs): 2,029864
_________________________________________________________________________________________________________
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): 207,219716
Driver with highest ISR routine execution time: ndis.sys - Pilote NDIS 6.20, Microsoft Corporation
Highest reported total ISR routine time (%): 0,190393
Driver with highest ISR total time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation
Total time spent in ISRs (%) 0,339317
ISR count (execution time <250 µs): 11597735
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µ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): 11188,927318
Driver with highest DPC routine execution time: ndis.sys - Pilote NDIS 6.20, Microsoft Corporation
Highest reported total DPC routine time (%): 2,389980
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.
Total time spent in DPCs (%) 2,929005
DPC count (execution time <250 µs): 53569274
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 4717
DPC count (execution time 1000-1999 µs): 929
DPC count (execution time 2000-3999 µs): 9
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: avgidsagenta.exe
Total number of hard pagefaults 35178
Hard pagefault count of hardest hit process: 4660
Highest hard pagefault resolution time (µs): 1415848,073517
Total time spent in hard pagefaults (%): 3,425926
Number of processes hit: 61
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 318,665925
CPU 0 ISR highest execution time (µs): 203,609023
CPU 0 ISR total execution time (s): 27,855491
CPU 0 ISR count: 6805711
CPU 0 DPC highest execution time (µs): 11188,927318
CPU 0 DPC total execution time (s): 181,768510
CPU 0 DPC count: 32851874
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 275,893928
CPU 1 ISR highest execution time (µs): 201,717627
CPU 1 ISR total execution time (s): 16,780447
CPU 1 ISR count: 1595848
CPU 1 DPC highest execution time (µs): 1741,675856
CPU 1 DPC total execution time (s): 144,572345
CPU 1 DPC count: 6790153
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 200,080109
CPU 2 ISR highest execution time (µs): 207,219716
CPU 2 ISR total execution time (s): 12,766159
CPU 2 ISR count: 1598626
CPU 2 DPC highest execution time (µs): 1770,232247
CPU 2 DPC total execution time (s): 140,089804
CPU 2 DPC count: 7082913
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 228,538801
CPU 3 ISR highest execution time (µs): 200,710109
CPU 3 ISR total execution time (s): 13,438953
CPU 3 ISR count: 1597550
CPU 3 DPC highest execution time (µs): 1754,091896
CPU 3 DPC total execution time (s): 145,073836
CPU 3 DPC count: 6849994
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 1:26:59 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: FC-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: LIFEBOOK AH530, FUJITSU, FJNBB06
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz
Logical processors: 4
Processor groups: 1
RAM: 3892 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2394 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): 1055723,059695
Average measured interrupt to process latency (µs): 7,094048
Highest measured interrupt to DPC latency (µs): 1055668,737882
Average measured interrupt to DPC latency (µs): 2,029864
_________________________________________________________________________________________________________
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): 207,219716
Driver with highest ISR routine execution time: ndis.sys - Pilote NDIS 6.20, Microsoft Corporation
Highest reported total ISR routine time (%): 0,190393
Driver with highest ISR total time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation
Total time spent in ISRs (%) 0,339317
ISR count (execution time <250 µs): 11597735
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µ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): 11188,927318
Driver with highest DPC routine execution time: ndis.sys - Pilote NDIS 6.20, Microsoft Corporation
Highest reported total DPC routine time (%): 2,389980
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.
Total time spent in DPCs (%) 2,929005
DPC count (execution time <250 µs): 53569274
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 4717
DPC count (execution time 1000-1999 µs): 929
DPC count (execution time 2000-3999 µs): 9
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: avgidsagenta.exe
Total number of hard pagefaults 35178
Hard pagefault count of hardest hit process: 4660
Highest hard pagefault resolution time (µs): 1415848,073517
Total time spent in hard pagefaults (%): 3,425926
Number of processes hit: 61
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 318,665925
CPU 0 ISR highest execution time (µs): 203,609023
CPU 0 ISR total execution time (s): 27,855491
CPU 0 ISR count: 6805711
CPU 0 DPC highest execution time (µs): 11188,927318
CPU 0 DPC total execution time (s): 181,768510
CPU 0 DPC count: 32851874
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 275,893928
CPU 1 ISR highest execution time (µs): 201,717627
CPU 1 ISR total execution time (s): 16,780447
CPU 1 ISR count: 1595848
CPU 1 DPC highest execution time (µs): 1741,675856
CPU 1 DPC total execution time (s): 144,572345
CPU 1 DPC count: 6790153
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 200,080109
CPU 2 ISR highest execution time (µs): 207,219716
CPU 2 ISR total execution time (s): 12,766159
CPU 2 ISR count: 1598626
CPU 2 DPC highest execution time (µs): 1770,232247
CPU 2 DPC total execution time (s): 140,089804
CPU 2 DPC count: 7082913
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 228,538801
CPU 3 ISR highest execution time (µs): 200,710109
CPU 3 ISR total execution time (s): 13,438953
CPU 3 ISR count: 1597550
CPU 3 DPC highest execution time (µs): 1754,091896
CPU 3 DPC total execution time (s): 145,073836
CPU 3 DPC count: 6849994
_________________________________________________________________________________________________________
soundgeek
2059
AFicionado·a
Membre depuis 10 ans
- < Liste des sujets
- Charte