Results 1 to 4 of 4
  1. #1
    2 Star Lounger
    Join Date
    Feb 2003
    Posts
    120
    Thanks
    3
    Thanked 2 Times in 2 Posts

    Force kernel to not page: always be resident? (XP SP2)

    Is it possible to force the Kernel to be always resident: that is, to defeat the paging of Kernel code? I have gobs of physical memory, and it seems to me that not paging the Kernel might help performance.

    Thanks
    Bob Chapman

  2. #2
    Administrator
    Join Date
    Mar 2001
    Location
    St Louis, Missouri, USA
    Posts
    23,572
    Thanks
    5
    Thanked 1,057 Times in 926 Posts

    Re: Force kernel to not page: always be resident? (XP SP2)

    Yes, if you are willing to change a setting in the registry. Under HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSe ssion ManagerMemory Management change the value in the REG_DWORD DisablePagingExecutive from 0 to 1. Re-boot.

    Joe
    Joe

  3. #3
    Platinum Lounger
    Join Date
    Jan 2001
    Location
    Quedgeley, Gloucester, England
    Posts
    5,333
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Force kernel to not page: always be resident?

    Bob

    You have, of course, considered the idea that Microsoft's memory handler tries to optimise performance even if you have 1.0 gob of memory, and trying to second-guess it may not improve matters much?

    It would be interesting to hear if you find it makes any noticeable difference...!

    John
    <font face="Script MT Bold"><font color=blue><big><big>John</big></big></font color=blue></font face=script>

    Ita, esto, quidcumque...

  4. #4
    2 Star Lounger
    Join Date
    Feb 2003
    Posts
    120
    Thanks
    3
    Thanked 2 Times in 2 Posts

    Re: Force kernel to not page: always be resident?

    Well, guys, I tried the suggestion, for which I thank you. However, it didn't seem to change Windows' operation at all! When I look at Windows Task Manager, it gives the Kernel size as 60 to 100 MB, 20MB resident, and the rest paged. In addition to not changing Windows' behavior, Windows was unhappy on boot-up, claiming it couldn't locate 4 modules.

    In any case, I've retreated to what I had before trying this.

    Bob

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •