Quote:
Originally posted by AlecStaar
Could be! This is one setting I have steered clear of, & have not even experimented with to be honest...
Same here always wondered what it meant, but now one says he gains performance. But the credibility of the advice is limited since he forgets that a page is 4 kbyte. So I wanted to check if anyone had any information of this registry entry.
Quote:
but I really DO think it can be used for granularity control of the diskcache itself, or ANY memory directed for System Use vs. UserMode application use (in combination with the other settings in that section, like LargeSystemCache in the registry MemoryManagement area).
It really depends of how it is implemented. I hope disk cache is not allowed to be paged, would be a really strange implementation . So one could actually limit how much RAM the kernel services should be able to grap (Without affecting the User Proces memory block). So if setting this value to 200 mb and using the entry LargeSystemCache(Server Service) then it should be limited to a 200 mb of RAM along with rest of the of kernel stuff. Avoiding the thing with exhausting memory when copying large files over a network. (Ofcourse this is just me guessing, as it requires that SystemCache means how much of the kernel memory block should be kept in memory)
Quote:
That is my understanding of it also... you can stop the kernel from paging itself though, with another entry in that area:
DisablePagingExecute (set that to Decimal 1)
As far I have read it is only the kernel core(Whatever that is) and drivers which is forced to be kept in memory.
Quote:
Others that are probably in play there are (just from their names & I am SURE you agree) are:
IoPageLockLimit (this one I know & work with)
This should be on the User Proces level(Not in kernel memory block). Assigning a certain amount of memory for each user proces.
Quote:
NonPagedPoolQuota (this one I have read about, but steer clear of)
NonPagedPoolSize (this one I have read about, but steer clear of)
PagedPoolSize (this one I have read about, but steer clear of)
I hope these entries specify how the memory management is for all of the 4 gb of memory and not just the kernel block.
Quote:
And, with Terminal Server?
SessionPoolSize (never worked with it)
SessionViewSize (never worked with it, DIRECTLY, in the registry at least)
I haven't used Terminal Server, but most of the articles, I have found about SystemPages, is about the terminal server and the problems about getting enough memory for it.
Quote:
This is a LONG read in this reply BUT DO READ IT, it may help you understand how this madness works at a VERY low level:
Sounds like something was really fubar. But I guess that is I/O programming in a nutshell.
Quote:
P.S.=> Snakefoot, I would like to hear more here on how your experimentations there go with those settings
I'm just looking into this to satisfy my curiosity. I'm not trying to solve some problem, besides finding out why the information about this little entry is a bit conflicting.
I think I will find some one to do a single experiment for me and that is to enable LargeSystemCache and at the same time limit the SystemPages. And then see if it will avoid the memory hogging thing when copying large files.