Paul, > On Wednesday 16 November 2011 at 06:04 Dmitry Yemanov wrote: > > > Also, some > > Windows versions are suspected in giving the file system cache too > > high priority thus possibly swapping out the pages of the process > > working set, so a largish internal page cache could prove itself to be > > a bad idea in this case. > > > > Do you know which windows versions?
It affects all x64 deployments of Win7, Win2003 and Win2008 (non-R2). In the case of Win2008R2 x64 systems, the new Dynamic Cache Service will limit file cache to 90% of physical RAM by default. This setting may not be appropriate and need adjustment if the amount of application/service memory (not working memory) required for the server exceeds 10%. In our case, for servers with 6GB-9GB we have set the file cache to 30-50% of memory due to the unpredictable number of classic FB engine processes that can be created (can vary from 75 to150/200), even with FB cache set to 75 pages (@ 8KB), and other application memory requirements. Naturally, as the amount of RAM increases we can increase the file cache, but on a case by case basis. Sean ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
