Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!hookup!swrinde!news.dell.com!tadpole.com!uunet!newsgate.watson.ibm.com!watnews.watson.ibm.com!bocanews.bocaraton.ibm.com!news
From: voodoo@vnet.ibm.com
Subject: Re: VisualAge, requirements
Sender: news@bocanews.bocaraton.ibm.com (News Admin ID)
Message-ID: <CyAsty.13r9@bocanews.bocaraton.ibm.com>
Date: Wed, 26 Oct 1994 20:56:22 GMT
Lines: 20
References: <AAQpChkO13@rrg.msk.su>
Nntp-Posting-Host: help06.raleigh.ibm.com
Organization: IBM Southeast Region Solution Center
X-Newsreader: IBM NewsReader/2 v1.00

In <AAQpChkO13@rrg.msk.su>, Vadim Povar <vf@rrg.msk.su> writes:
>
>Usually it is said that VisualAge asks 16M for its normal
>working. But i know the statement (of friend of mine) that
>it is not so. That is VisualAge works ok under 32M of memory
>and witnin 16M it works like VW 1.0 works under 4M.
>Can anybody somehow comment it ?
>
>Thanks in advance,
>Vadim
>

Well, as a user and former employer working on the design side I'd
say that with 16M it *STILL* thinks it is a dog with its legs nailed
to the floor (i.e., doesn't move all that fast).  In actuality, response
time is fairly quick for those parts that have focus.  To really make 
it run better I'd recommend getting the fastest damn disk you can; most
of your wait time is on disk I/O (either intentional or swapper work).

 

