이전에는 불쾌한 pagefault가있는 스레드가 있었는데 주요 범인은 내 HDD가 실제로 고장났다는 것입니다. 이번 주에 새로운 SSD를 받고 Windows 7을 다시 설치 한 이후로 상황이 훨씬 빨라졌습니다. 딸꾹질이있는 여러 게임의 매우 낮은 설정에서 최대 설정으로 이동했습니다. 나쁜 HDD가 내 성능에 병목 현상을 일으킨 기간이 정말 우울 해졌고 거부당했습니다.
어쨌든, Latencymon은 아래에 올릴뿐만 아니라 xperf를 붙여 넣을 것입니다. 다음에 볼 위치에 대한 도움이 필요하면 생각할 수있는 모든 드라이버를 설치했습니다. SSD가 최신 펌웨어로 업데이트되었고 BIOS에서 Intel Speed Tech가 비활성화되었으며 BIOS가 최신 상태입니다 (Sabertooth p67 3602 버전). Windows에서도 고성능이 선택되었습니다.
XPERF : https://drive.google.com/file/d/0B597DIrOwkw0UHF2THlQaGlESk0/view?usp=sharing
CONCLUSION
_________________________________________________________________________________________________________
Your system seems to have difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. 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:02:02 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: TRISTIANLEW
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: ASUSTeK Computer INC., SABERTOOTH P67
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
Logical processors: 8
Processor groups: 1
RAM: 12255 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3407.0 MHz
Measured CPU speed: 2859.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): 1115.986248
Average measured interrupt to process latency (µs): 2.764362
Highest measured interrupt to DPC latency (µs): 182.091456
Average measured interrupt to DPC latency (µs): 0.893639
_________________________________________________________________________________________________________
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): 209.179043
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.033012
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0.065645
ISR count (execution time <250 µs): 153822
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): 270.250073
Driver with highest DPC routine execution time: tcpip.sys - TCP/IP Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 0.038182
Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 0.133808
DPC count (execution time <250 µs): 567636
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µ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 343
Hard pagefault count of hardest hit process: 89
Highest hard pagefault resolution time (µs): 61875.318168
Total time spent in hard pagefaults (%): 0.042098
Number of processes hit: 11
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 3.493773
CPU 0 ISR highest execution time (µs): 209.179043
CPU 0 ISR total execution time (s): 0.645163
CPU 0 ISR count: 153822
CPU 0 DPC highest execution time (µs): 245.619607
CPU 0 DPC total execution time (s): 1.250163
CPU 0 DPC count: 545089
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 1.547568
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): 270.250073
CPU 1 DPC total execution time (s): 0.003498
CPU 1 DPC count: 407
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1.335016
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): 205.423540
CPU 2 DPC total execution time (s): 0.015915
CPU 2 DPC count: 5349
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 1.739508
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): 178.61990
CPU 3 DPC total execution time (s): 0.002303
CPU 3 DPC count: 260
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0.946584
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): 164.648665
CPU 4 DPC total execution time (s): 0.020333
CPU 4 DPC count: 7698
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 1.600787
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): 0.0
CPU 5 DPC total execution time (s): 0.0
CPU 5 DPC count: 0
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 1.035665
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): 163.171705
CPU 6 DPC total execution time (s): 0.022867
CPU 6 DPC count: 8834
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1.814152
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): 0.0
CPU 7 DPC total execution time (s): 0.0
CPU 7 DPC count: 0
_________________________________________________________________________________________________________
드라이버, HDD 펌웨어 등으로 페이지 결함을 수정할 수 없으며, 이는 최대 메모리 소비의 결과입니다. "결함"이라고하지만 실패는 아닙니다.
—
ilkhd
안녕하세요, 정보 주셔서 감사합니다. 내가 얻는 대부분의 경우, 나는 두 가지를 이해하려고한다고 가정합니다. 프로그램을로드 할 때 수백 페이지 오류가 발생하는 것이 '정상'입니까? 다른 부분은 hal.dll에 대해 ~ 100k ISR 수를 얻는 것이 정상인지 이해하는 것입니다. 케이스 앞면의 무선 N USB 어댑터를 인터넷 용 USB 3.0 슬롯에 사용합니다. 이것이 비활성화되면 여전히 페이지 오류가 발생하지만 Latencymon 보고서는 ISR 수가 거의 동일하지만 대기 시간에 대한 높은 보고서없이 정상적으로 돌아옵니다. 그것은 현재 3 층 건물에서 인터넷의 유일한 수단입니다.
—
Naitsirt
또한 내 PC가 완전히 안정적 인 것처럼 현명한 성능을 추가하고 싶습니다. 이번 주에 HDD를 교체했는데 문제의 큰 원인 인 것 같았지만 LatencyMon의 모든 숫자가 동일하게 보이기 때문에 현재 내 컴퓨터에 다른 문제가 없는지 확인하고 싶습니다.
—
Naitsirt
걱정하기 전에 페이지 오류가 무엇인지 읽었습니다.- en.wikipedia.org / wiki / Page_fault 디스크에 '페이지 된'파일로 메모리를 사용하여 OS가 메모리 요구 사항을 처리하는 방식의 '자연적인'부분입니다. 실제 물리적 RAM 대신.
—
Tetsujin