| Subject: FileSystemCache |
| Group: microsoft.public.winternals |
| Date: 1/18/2008 6:20:48 PM |
| From: Megan Kielman [Email Address Protection] |
I did some reading in the Winternals Book and online but have some questions about the FileSystemCache. 1. Pg. 664 of the Winterals Book has a table showing size and location of the system cache. It says that on x64, it can range from 64MB-1024MB depending on RAM and physical memory, but I read somewhere (http://technet2.microsoft.com/windowsserver/en/library/efa621bd-a031-4461-9e72-59197a7507b61033.mspx?mfr=true), that is can grow to physical memory. If I specify LargeSystemCache in the registry, how can I determine the size of the cache? 2. Is SystemCache memory in a different pool of memory then NonPagedPool? 3. Is System Cache determined at boot or does it grow? |
| Back |
| Subject: Re: FileSystemCache |
| Group: microsoft.public.winternals |
| Date: 2/18/2008 4:55:12 PM |
| From: Megan Kielman [Email Address Protection] |
Is there anyone who can help me with my questions? I am having a difficult time finding answers online. Megan Kielman wrote: > I did some reading in the Winternals Book and online but have some > questions about the FileSystemCache. > > 1. Pg. 664 of the Winterals Book has a table showing size and location > of the system cache. It says that on x64, it can range from 64MB-1024MB > depending on RAM and physical memory, but I read somewhere > (http://technet2.microsoft.com/windowsserver/en/library/efa621bd-a031-4461-9e72-59197a7507b61033.mspx?mfr=true), > that is can grow to physical memory. If I specify LargeSystemCache in > the registry, how can I determine the size of the cache? > > 2. Is SystemCache memory in a different pool of memory then NonPagedPool? > > 3. Is System Cache determined at boot or does it grow? |
| Back |
| Subject: Re: FileSystemCache |
| Group: microsoft.public.winternals |
| Date: 2/19/2008 11:16:49 AM |
| From: compositor [Email Address Protection] |
Megan Kielman wrote: > Is there anyone who can help me with my questions? I am having a > difficult time finding answers online. > > Megan Kielman wrote: >> I did some reading in the Winternals Book and online but have some >> questions about the FileSystemCache. >> >> 1. Pg. 664 of the Winterals Book has a table showing size and location >> of the system cache. It says that on x64, it can range from >> 64MB-1024MB depending on RAM and physical memory, but I read somewhere >> (http://technet2.microsoft.com/windowsserver/en/library/efa621bd-a031-4461-9e72-59197a7507b61033.mspx?mfr=true), >> that is can grow to physical memory. If I specify LargeSystemCache in >> the registry, how can I determine the size of the cache? >> >> 2. Is SystemCache memory in a different pool of memory then NonPagedPool? >> >> 3. Is System Cache determined at boot or does it grow? It is all managed by Windows, so therefore the more RAM you have the better and the greater the size of your instruction buffer(s), even better still. |
| Back |
| Subject: Re: FileSystemCache |
| Group: microsoft.public.winternals |
| Date: 2/21/2008 1:48:22 PM |
| From: Megan Kielman [Email Address Protection] |
Thanks for the reply. So are you saying that the memory used for the file system cache is from user mode? compositor wrote: > Megan Kielman wrote: >> Is there anyone who can help me with my questions? I am having a >> difficult time finding answers online. >> >> Megan Kielman wrote: >>> I did some reading in the Winternals Book and online but have some >>> questions about the FileSystemCache. >>> >>> 1. Pg. 664 of the Winterals Book has a table showing size and >>> location of the system cache. It says that on x64, it can range from >>> 64MB-1024MB depending on RAM and physical memory, but I read >>> somewhere >>> (http://technet2.microsoft.com/windowsserver/en/library/efa621bd-a031-4461-9e72-59197a7507b61033.mspx?mfr=true), >>> that is can grow to physical memory. If I specify LargeSystemCache >>> in the registry, how can I determine the size of the cache? >>> >>> 2. Is SystemCache memory in a different pool of memory then >>> NonPagedPool? >>> >>> 3. Is System Cache determined at boot or does it grow? > > It is all managed by Windows, so therefore the more RAM you have the > better and the greater the size of your instruction buffer(s), even > better still. |
| Back |
| Subject: Re: FileSystemCache |
| Group: microsoft.public.winternals |
| Date: 2/22/2008 2:24:38 PM |
| From: compositor [Email Address Protection] |
Megan Kielman wrote: > Thanks for the reply. So are you saying that the memory used for the > file system cache is from user mode? Basically yes and depending on your processor, which may or may not allow large paging filesystems, the size of the pagefile may be restricted. > compositor wrote: >> Megan Kielman wrote: >>> Is there anyone who can help me with my questions? I am having a >>> difficult time finding answers online. >>> >>> Megan Kielman wrote: >>>> I did some reading in the Winternals Book and online but have some >>>> questions about the FileSystemCache. >>>> >>>> 1. Pg. 664 of the Winterals Book has a table showing size and >>>> location of the system cache. It says that on x64, it can range from >>>> 64MB-1024MB depending on RAM and physical memory, but I read >>>> somewhere >>>> (http://technet2.microsoft.com/windowsserver/en/library/efa621bd-a031-4461-9e72-59197a7507b61033.mspx?mfr=true), >>>> that is can grow to physical memory. If I specify LargeSystemCache >>>> in the registry, how can I determine the size of the cache? >>>> >>>> 2. Is SystemCache memory in a different pool of memory then >>>> NonPagedPool? >>>> >>>> 3. Is System Cache determined at boot or does it grow? >> >> It is all managed by Windows, so therefore the more RAM you have the >> better and the greater the size of your instruction buffer(s), even >> better still. |
| Back |
| Subject: Re: FileSystemCache |
| Group: microsoft.public.winternals |
| Date: 2/22/2008 2:38:43 PM |
| From: Megan Kielman [Email Address Protection] |
Ok - just so I am clear. Does this mean there is an advantage to have a x64 file server with a lot of memory so that it can be used for the file system cache? compositor wrote: > Megan Kielman wrote: >> Thanks for the reply. So are you saying that the memory used for the >> file system cache is from user mode? > > Basically yes and depending on your processor, which may or may not > allow large paging filesystems, the size of the pagefile may be restricted. > >> compositor wrote: >>> Megan Kielman wrote: >>>> Is there anyone who can help me with my questions? I am having a >>>> difficult time finding answers online. >>>> >>>> Megan Kielman wrote: >>>>> I did some reading in the Winternals Book and online but have some >>>>> questions about the FileSystemCache. >>>>> >>>>> 1. Pg. 664 of the Winterals Book has a table showing size and >>>>> location of the system cache. It says that on x64, it can range >>>>> from 64MB-1024MB depending on RAM and physical memory, but I read >>>>> somewhere >>>>> (http://technet2.microsoft.com/windowsserver/en/library/efa621bd-a031-4461-9e72-59197a7507b61033.mspx?mfr=true), >>>>> that is can grow to physical memory. If I specify LargeSystemCache >>>>> in the registry, how can I determine the size of the cache? >>>>> >>>>> 2. Is SystemCache memory in a different pool of memory then >>>>> NonPagedPool? >>>>> >>>>> 3. Is System Cache determined at boot or does it grow? >>> >>> It is all managed by Windows, so therefore the more RAM you have the >>> better and the greater the size of your instruction buffer(s), even >>> better still. |
| Back |
| Subject: Re: FileSystemCache |
| Group: microsoft.public.winternals |
| Date: 2/24/2008 3:32:02 PM |
| From: compositor [Email Address Protection] |
Megan Kielman wrote: > Ok - just so I am clear. Does this mean there is an advantage to have a > x64 file server with a lot of memory so that it can be used for the file > system cache? To answer your question, the more memory you have the less chance that any will be cached to files unless of course there is a "smart cache" which knows which type of data can be put to page and which can't, however it's unlikely that this kind of system exists. The best way to understand how all this works is to go back and read up on how the earlier windows systems worked with virtual memory and so forth as it was easier to "tweak" these systems but now they tend to leave it up to the OS itself to manage, otherwise you can prevent it from going to virtual memory at all but I know this isn't a solution not even for me. Best of luck > > compositor wrote: >> Megan Kielman wrote: >>> Thanks for the reply. So are you saying that the memory used for the >>> file system cache is from user mode? >> >> Basically yes and depending on your processor, which may or may not >> allow large paging filesystems, the size of the pagefile may be >> restricted. >> >>> compositor wrote: >>>> Megan Kielman wrote: >>>>> Is there anyone who can help me with my questions? I am having a >>>>> difficult time finding answers online. >>>>> >>>>> Megan Kielman wrote: >>>>>> I did some reading in the Winternals Book and online but have some >>>>>> questions about the FileSystemCache. >>>>>> >>>>>> 1. Pg. 664 of the Winterals Book has a table showing size and >>>>>> location of the system cache. It says that on x64, it can range >>>>>> from 64MB-1024MB depending on RAM and physical memory, but I read >>>>>> somewhere >>>>>> (http://technet2.microsoft.com/windowsserver/en/library/efa621bd-a031-4461-9e72-59197a7507b61033.mspx?mfr=true), >>>>>> that is can grow to physical memory. If I specify >>>>>> LargeSystemCache in the registry, how can I determine the size of >>>>>> the cache? >>>>>> >>>>>> 2. Is SystemCache memory in a different pool of memory then >>>>>> NonPagedPool? >>>>>> >>>>>> 3. Is System Cache determined at boot or does it grow? >>>> >>>> It is all managed by Windows, so therefore the more RAM you have the >>>> better and the greater the size of your instruction buffer(s), even >>>> better still. |
| Back |