Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!gatech!howland.reston.ans.net!swrinde!elroy.jpl.nasa.gov!usc!crash!starbase.cts.com!webber
From: webber@cts.com (Paul Webber)
Subject: Re: VW 2.0 MemoryPolicy (was: VW2.0 Slowing Down)
Organization: Prism Solutions, Inc.
Date: Tue, 20 Jun 1995 16:28:32 GMT
Message-ID: <webber.6.04F24534@cts.com>
X-Newsreader: Trumpet for Windows [Version 1.0 Rev B final beta #4]
References: <3rfjt4$lq8@noc.tor.hookup.net> <DA1y0p.299@hplb.hpl.hp.com> <3s5ljc$m66@gold.interlog.com>
Sender: news@crash.cts.com (news subsystem)
Nntp-Posting-Host: starbase.cts.com
Lines: 47

In article <3s5ljc$m66@gold.interlog.com> oo@interlog.com (Oliver Oey) writes:

>gw@hplb.hpl.hp.com (Gunther Walther) writes:

>>In article <3rfjt4$lq8@noc.tor.hookup.net> you wrote:
>>: I have been using VW2.0 since last august, but not full time (we are
>>: basically evaluating Smalltalk for out company).

>>: I am running on WFWG 3.11 on a 486/66 with 16Mb of memory with a 20Mb
>>: swap.  I have 32bit Disk/File access enabled.

I have 20Mb memory and 50 Mb swap, though I never go into swap (i.e. no disk 
light/noise)

>>: I do not have a large application, my image runs around 5.5Mb.

Mine is 6.4Mb

>>: I find that after working for a few weeks response gets worse.  A mouse
>>: button click may take a second or two to respond.  Its almost as if the
>>: response is delayed, once it gets rolling its OK.  I am not seeing
>>: a Garbage Collection cursor appear.  I do lots of fileIns because I
>>: move things from the office to home and back (We are not using Envy yet).
>>: I wonder if anyone has experienced this? and/or if anyone has any simpler
>>: solution?

I am using Envy and the problem happens within a few min. of opening the 
image.

>I don't know how big your change file is but looks like your change 
file >could be getting quite big due to all those file-in's.  Try condensing 
>the change file.  I don't remember the exact expression accomplish this 
>but you could just look for the implementor of "condens*".

Envy doesn't have a change file.
 
>Oliver Oey                                email: oo@interlog.com

With ParcPlace helping, it turns out to be the IGC, see chapter 20 VW Users 
Guide.  By disabling all calls to the IGC by modifing the MemoryPolicy I was 
able to get "control" back.  But, you have to do manual garbageCollection more 
often and ParcPlace says that this is not a fix but another way to track 
down the problem ;-)

Paul
webber@cts.com

