Commencer une nouvelle conversation

Solved!

Aller à la solution

1 Rookie

 • 

2  messages

18

19 juin 2024 09:35

Problème de latence

Bonjour,

J'ai mis en place un PowerEdge R250 avec Windows Server 2016 bare-metal.

Le serveur n'a pas de carte PERC, j'utilise du RAID logiciel au niveau du BIOS (S150 il me semble)

Windows est installé sur le HDD Dell (non raid)

J'ai créé un RAID 0 de 2xSamsung Pro pour les data, Windows voit ce volume que j'ai formaté en D:\

Dès l'installation, le serveur est lent et pas réactif du tout.

Sous le gestionnaire de tâche Windows, le CPU est toujours à 1% et capé à 0.2GHz.

Conf Windows avec performance élevé CPU 100%.

Avec du mal, j'ai pu installer tous les drivers manquants (DellAssistant n'a rien installé du tout).

J'ai utilisé LatencyMon et j'ai découvert la cause des lenteurs

Pouvez-vous m'aiguillez sur comment résoudre le problème ?

Merci

_________________________________________________________________________________________________________
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  1:23:56  (h:mm:ss) on all processors.

 

 

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        *nom du serveur*
OS version:                                           Windows Server 2016, 10.0, version 2009, build: 20348 (x64)
Hardware:                                             PowerEdge R250, Dell Inc.
BIOS:                                                 1.8.1
CPU:                                                  GenuineIntel Intel(R) Xeon(R) E-2314 CPU @ 2.80GHz
Logical processors:                                   4
Processor groups:                                     1
Processor group size:                                 4
RAM:                                                  8038 MB total

 

 

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI):                             2808 MHz
Reported CPU speed (registry):                        2808 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):   9332,20
Average measured interrupt to process latency (µs):   53,537761

 

Highest measured interrupt to DPC latency (µs):       9226,70
Average measured interrupt to DPC latency (µs):       16,780147

 

 

_________________________________________________________________________________________________________
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):              46481,059117
Driver with highest ISR routine execution time:       storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

 

Highest reported total ISR routine time (%):          0,007541
Driver with highest ISR total time:                   storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

 

Total time spent in ISRs (%)                          0,007593

 

ISR count (execution time <250 µs):                   38975
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-1000 µs):               100
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):              46573,472934
Driver with highest DPC routine execution time:       bcraid660.sys - RAIDCore MiniPort, Dell Inc.

 

Highest reported total DPC routine time (%):          0,030891
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 (%)                          0,167926

 

DPC count (execution time <250 µs):                   1275380
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-10000 µs):              1490
DPC count (execution time 1000-2000 µs):              298
DPC count (execution time 2000-4000 µs):              25
DPC count (execution time >=4000 µs):                 12

 

 

_________________________________________________________________________________________________________
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                       10668
Hard pagefault count of hardest hit process:          3901
Number of processes hit:                              58

 

 

_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       230,391035
CPU 0 ISR highest execution time (µs):                46481,059117
CPU 0 ISR total execution time (s):                   1,529553
CPU 0 ISR count:                                      39088
CPU 0 DPC highest execution time (µs):                2768,445513
CPU 0 DPC total execution time (s):                   16,110530
CPU 0 DPC count:                                      654993
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       74,938130
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):                6218,061610
CPU 1 DPC total execution time (s):                   6,136722
CPU 1 DPC count:                                      171697
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       82,462480
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):                1112,017094
CPU 2 DPC total execution time (s):                   3,217342
CPU 2 DPC count:                                      107782
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       74,708698
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):                46573,472934
CPU 3 DPC total execution time (s):                   8,363385
CPU 3 DPC count:                                      342733

Moderator

 • 

3.5K  messages

19 juin 2024 13:39

Bonjour,

le R250 n'est pas supporté avec Windows 2016, c'est très probable que c'est la cause du probleme.

Ici le OS supporté par la machine

Supported Operating Systems | Dell US

Cordialement

Aucun événement trouvé !

Top