Latenz

Antworten
Buellerich
Aktiver Hörer
Beiträge: 261
Registriert: 31.01.2015, 23:08

Latenz

Beitrag von Buellerich »

Guten Tag zusammen,

ich habe gestern den Explorer ausprobieren wollen, für den ich mich entschieden habe und war einigermassen gefrustet, als es einen bösen Drop-Out gab. Der Rechner ist bereits getweakt, indem ich sämtliche Energie-Einsparoptionen deselektiert habe. Zudem habe ich den Task Schedule wie empfohlen auf Hintergrund gestellt und zudem die minimale Prozessorleistung auf 100% gestellt. Ich habe sogar vorhin den Netzwerkadapter (WLAN plus Bluetooth) abgeklemmt.

Da der Drop Out irgendwann kam, ist wohl nicht davon auszugehen, dass das mit der in der Software gewählten Latenz zu tun hat, sonst wäre das Problem wohl ständig. In Foobar habe ich die WASAPI Event Style mit der standardmäßigen 25 MicroSek. Latenz gewählt.

Über Latency Mon bekomme ich folgendes:

Code: Alles auswählen

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. Also one or more ISR 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  0:35:43  (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        BÜLLERICH-PC
OS version:                                           Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware:                                             P6635, Medion
CPU:                                                  GenuineIntel Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Logical processors:                                   4
Processor groups:                                     1
RAM:                                                  3992 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed:                                   2494,0 MHz
Measured CPU speed:                                   1716,0 MHz (approx.)

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):   26254,363754
Average measured interrupt to process latency (µs):   5,597080

Highest measured interrupt to DPC latency (µs):       2530,813111
Average measured interrupt to DPC latency (µs):       2,388128


_________________________________________________________________________________________________________
 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):              1242,052927
Driver with highest ISR routine execution time:       i8042prt.sys - i8042-Anschlusstreiber, Microsoft Corporation

Highest reported total ISR routine time (%):          0,020578
Driver with highest ISR total time:                   i8042prt.sys - i8042-Anschlusstreiber, Microsoft Corporation

Total time spent in ISRs (%)                          0,050801

ISR count (execution time <250 µs):                   479247
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-999 µs):                3
ISR count (execution time 1000-1999 µs):              3
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):              2542,934242
Driver with highest DPC routine execution time:       ndis.sys - NDIS 6.20-Treiber, Microsoft Corporation

Highest reported total DPC routine time (%):          0,031584
Driver with highest DPC total execution time:         iaStor.sys - Intel Rapid Storage Technology driver - x64, Intel Corporation

Total time spent in DPCs (%)                          0,159989

DPC count (execution time <250 µs):                   1389321
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-999 µs):                985
DPC count (execution time 1000-1999 µs):              2133
DPC count (execution time 2000-3999 µs):              4
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                       41383
Hard pagefault count of hardest hit process:          16399
Highest hard pagefault resolution time (µs):          10276340,154370
Total time spent in hard pagefaults (%):              5,764346
Number of processes hit:                              21


_________________________________________________________________________________________________________
 PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       11,047479
CPU 0 ISR highest execution time (µs):                161,026464
CPU 0 ISR total execution time (s):                   0,8390
CPU 0 ISR count:                                      172655
CPU 0 DPC highest execution time (µs):                2542,934242
CPU 0 DPC total execution time (s):                   7,193074
CPU 0 DPC count:                                      984662
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       14,205212
CPU 1 ISR highest execution time (µs):                1242,052927
CPU 1 ISR total execution time (s):                   3,517213
CPU 1 ISR count:                                      306598
CPU 1 DPC highest execution time (µs):                2332,740176
CPU 1 DPC total execution time (s):                   6,112366
CPU 1 DPC count:                                      308720
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       1,937153
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):                1230,995589
CPU 2 DPC total execution time (s):                   0,273932
CPU 2 DPC count:                                      54156
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       5,523696
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):                221,900561
CPU 3 DPC total execution time (s):                   0,139775
CPU 3 DPC count:                                      44905
_________________________________________________________________________________________________________
Hat irgend jemand ähnliche Erfahrungen und es in den Griff bekommen?

Viele Grüße

Sascha

P.S.: Während des Tests lief der Laptop Rechner im Leerlauf.....
Bild
Antworten