Newsgroups: comp.client-server,comp.lang.c++,comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!europa.chnt.gtegsc.com!news.umbc.edu!haven.umd.edu!purdue!lerc.nasa.gov!magnus.acs.ohio-state.edu!math.ohio-state.edu!uwm.edu!news.moneng.mei.com!hookup!interlog.com!news1.fonorola.net!fonorola!news!dbuck
From: dbuck@infoweb.magi.com (David Buck)
Subject: Re: RAM req for C/S app with SmallTalk or C++
Sender: news@magi.com
Message-ID: <DAHGww.B34@magi.com>
Date: Tue, 20 Jun 1995 18:05:20 GMT
References: <3s4l7t$jpb@crcnis3.unl.edu>
Nntp-Posting-Host: infoweb.magi.com
Organization: Magi Data Consulting
Lines: 28
Xref: glinda.oz.cs.cmu.edu comp.client-server:11159 comp.lang.c++:134362 comp.lang.smalltalk:24831

In article <3s4l7t$jpb@crcnis3.unl.edu>,
Mark Horan <horan@csealumni.unl.edu> wrote:
>
>	I am trying to get an idea of RAM requirements for a medium to
>large sized client/Server database application using Digitalk's Smalltalk or
>Microsofts Visual C++ with MFC.  I was told (by Digitalk) that 8MB
>would run the application fine but that the startup might be slow.  I 
>wanted to know if people who have used it found this to be true.  As far
>as C++ I was wondering what the RAM requirements might be for the same
>app developed with MFC.
>
>Thanks for any help.

In Smalltalk V/Win32, You can run the base image in as little as 4 megs.  
NOTE:  You don't WANT to run the image in 4 Megs - it swaps like crazy 
and your application is unusably slow.  In tests with a medium-size 
application, we found that 8 Megs wasn't enough to comfortably run the 
application.  It would take 50 seconds to load.  After loading, the 
performance was acceptable, however.  With 12 Megs or more, the load time 
dropped to 13 seconds and the performance was good.

I hope this helps.

David Buck
dbuck@magi.com
The Object People


