Computer Chess Club Archives




Subject: Re: is the

Author: Ernst Walet

Date: 09:26:00 07/30/98

Go up one level in this thread

On July 30, 1998 at 09:46:06, Komputer Korner wrote:

>On July 30, 1998 at 02:37:19, Ernst Walet wrote:

>>With WIN95 System Monitor you can accomplisch the same, by looking at the
>>allocated memory minnus the disk cache size.  And this is waht I did.
>This is just not true. See below.
>Nimzo 98 takes up to 106Mb for a hash table in WIN NT on my 144Mb system. Nimzo
>3.5 takes up to the same amount in WIN 95 if you have 144Mb of RAM and without
>swapping. However on a system with only 40Mb of RAM, one cannot load more than
>about 18 Mb of RAM for a hash table in Nimzo 3.5 without terrible swapping on
>every move. Thus WIN 95 must grab about 20Mb of RAM for itself when it forms
>it's page file. The WIN 95 System Monitor is a sorry excuse for a reporting tool
>compared to the WIN NT 4 Task Manager but here are the findings after starting
>WIN 95 and Nimzo 3.5 on a system with 144 Mb of RAM.Allocated memory- 161.7Mb
>Free Memory- 16KOther Memory- 42.4 MbSwapfile Size - 18.5 Mb
>Swapfile in use- 2.7MbDiskcache size- 23.7MbLocked Memory- 27.4 Mb
>Swapfile defective- 0Swappable memory- 119.2Mb
>Now if anything is more confusing than this I haven't seen it.
>So if we take your equation we have 161.7Mb- 23.7Mb = 138Mb for a hash table
>which is NOT TRUE. The WIN 95 System Monitor is brain dead or else the entries
>mean somethimg else than what they read.
> That is one of
>the reasons why I like to stay in the WIN NT 4 environment.
>After shutting down Nimzo 3.5 , the amounts of the above table change to the
>following:Allocated memory-55.2MbFree Memory- 105.2MbOther Memory- 42.3Mb
>Swapfile Size - 2.7MbSwapfile in use- 2.7MbDiskcache size- 23.6 Mb
>Locked Memory- 26.9 MbSwapfile defective- 0Swappable memory- 12.8Mb
>When I shut down WIN 95, and restart the numbers there are very small changes in
>the numbers except that Swapfile size and Swapfile in use drop to 0 and Free
>Memory drops to 102.2 Mb.
>So it is all very confusing but it seems that unless you limit the vcache size
>in Windows system.ini WIN 95 will take some of your precious memory for itself.
>It seems that from the Free Memory numbers, WIN 95's system monitor doesn't know
>what the hell is going on. Maybe nobody knows. We do know that if you limit the
>vcache, some other input-output operations will be drastically affected so that
>isn't a satisfactory solution. But what is clear is that this drastically limits
>systems with smaller amounts of Systems with less than 64Mb of RAM.
>On my other WIN 95 system with 40 Mb of RAM, the amount of RAM clearly isn't
>enough. Perhaps some programs round up to the next hash table size instead of
>rounding down  and that would help to explain what happens (massive
>swapping)when I try to create 20Mb hash table or more on my system with 40 Mb of
>Komputer Korner

Well... if it's to complicated for you lets make it easier and put an
Minfilecache=1024 and a maxfilecache=1024 in the system.ini.

Now startup ie. fritz5 with the minimum hash size of 64KB.

In the system monitor only look at the allocated memory, and write down the
number.  I think you'll agree that 64KB can be considered as no hash in the
number you see.

Than increase the hashtablesize by 10 Megs, or whatever, and behold.... the
allocated memory in the system monitor increases with 10Megs as well!

Now with my 48 Megs i can increase the hashtable to 40Megs, the allocated memory
increases with 40 megs as well and the system swaps for about 3 minutes, and
then not again as long as fritz runs!


This page took 0 seconds to execute

Last modified: Thu, 15 Apr 21 08:11:13 -0700

Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.