RichardRudekatWork

RichardRudekatWork Richard​RudekatWork

Niner since 2013

Comments

  • Defrag Tools: #45 - WPT - File & Registry Analysis

    Does anybody know why or can confirm the limited capability of File I/O stacks captured on Windows 7x64, or Windows Server 2008R2 ?

    It seems to work fine on Windows 8 and Server 2012, which can obviously also be seen in the above Video. So it's become quite frustrating.

    To be clear, I'm talking specifically about when I add the Stack column to "File I/O Activity by Process, Thread, Type", switch to table view, then add\adjust the columns [*A].

    Symbols resolved, x64 registry setting, etc. See below.

    But I still only get "?!?" frames.

    [*A] Columns I typically use are in this order:
    Line#, Process, Event Type, Event Sub Type, FileName, Thread, Stack | Gold bar| etc ...

     

    Curiously, I do seem some stacks, but only under "System Activity", which is not even close to what I want.

    DETAILS

    Scenario 1:
    VMWare Player 5.0.2 build-1031769

    Line #ConfigurationValue
    3Product NameWindows Server 2008 R2 Enterprise
    4Build Lab7600.16385.amd64fre.win7_rtm.090713-1255
    5OS Version6.1
    6Build7600
    7Number of Processors2
    8Processor Speed3392 MHz
    9Hyper-Threading Enabled Processors0x0000000000000000
    10Memory Size2048 MB
    11Page Size4096 Bytes
    12Allocation Granularity65536 Bytes
    13Supported Power StatesS1 S4 S5
    14Boot DriveDisk 0 - Drive C - NTFS
    15ETW Internal Version25

     

    Scenario 2:Real PC - HP8200Elite (Hosting Scenario 1)

    Line #ConfigurationValue
    3Product NameWindows 7 Enterprise
    4Build Lab7601.18113.amd64fre.win7sp1_gdr.130318-1533
    5OS Version6.1
    6Build7601
    7Number of Processors8
    8Processor Speed3392 MHz
    9Hyper-Threading Enabled Processors0x00000000000000FF
    10Memory Size16342 MB
    11Page Size4096 Bytes
    12Allocation Granularity65536 Bytes
    13Supported Power StatesS3 S4 S5
    14Boot DriveDisk 0 - Drive C - NTFS
    15ETW Internal Version25

     

    Scenario 3 (Working fine, so this is FYI):

    Line #ConfigurationValue
    3Product NameWindows Server 2012 Standard
    4Build Lab9200.16581.amd64fre.win8_gdr.130410-1505
    5OS Version6.2
    6Build9200
    7Number of Processors2
    8Processor Speed2667 MHz
    9Hyper-Threading Enabled Processors0x0000000000000000
    10Memory Size2048 MB
    11Page Size4096 Bytes
    12Allocation Granularity65536 Bytes
    13Supported Power StatesS1 S4 S5
    14Boot DriveDisk 0 - Drive C - NTFS
    15ETW Internal Version42

     

    Things tried so far:

    1. Set and verified registry setting. Restarted many time since:

    reg add "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management" /v DisablePagingExecutive /t REG_DWORD /d 1

    2. Using Andrew's Fileio.cmd. As in:

    ...
    xperf -on PROC_THREAD+LOADER+FILENAME+FILE_IO+FILE_IO_INIT -stackwalk FileCreate+FileCleanup+FileClose+FileRead+FileWrite -BufferSize 1024 -MinBuffers 256 -MaxBuffers 256 -MaxFile 256 -FileMode Circular
    ...

    3. Using WPR with CPU and File IO enabled.

    4. Switched to Windows 8 x64 VM and saw it works fine - as per my original expectation on Windows 7x