Re: [Dev-C++] Compilation painfully slow

The issue of ram only comes up when you are already crunched for ram.  That's why the previous suggestion to monitor memory usage via Task Manager (or whatever was the appropriate application on '98).  64MB of ram may be sufficient for some machines and OS combinations.  The fact that the compiler runs slower than the previous version isn't indicative of a ram size problem, as the previous compiler version ran with the existing ram without problem, right?
 
I would first recommend disabling the header file cache that Dev-C++ tries to compile upon installation.  I've noticed that this takes significant time, and recompilation of the header file cache occurs frequently.  Then monitor the hard disk audibly to see if it is thrashing.  If it is thrashing then that is the indicia of more ram possibly being needed.
 
Some machines, especially laptops, are notoriously hard to open and add ram to, and opening them may possibly void the warranty if one is applicable.  Provided that compatible ram is available.  Buying more ram is great for towers such as Dell's Optiplex GX280 or such, but is a shotgun solution that should be investigated and verified before spending cash!

Josh McFarlane <da...@gm...> wrote:
On 7/26/05, Frankie Kam wrote:
> Dear All Dev C++ users
> 
> Does anyone know how to speed up the
> compilation process of Dev-C++?
> I'm running Win98 with a Celeron 1Gig machine. 64 Meg RAM.
> 
> Previously I had Dev-C++ version 4 and
> then yesterday I downloaded the latest version
> of Dev-C++ Bloodshed...and the compilation
> process takes a long time compared to the
> previous version.
> Any tips to speed things up a bit?
> 
> I remember my DOS days and Turbo C++ when
> compilation was a zip!
> 
> Thanks in advance (I hope).
> 
> regards
> Frankie Kam
> Coordinator SOCS SCM
> www.stamford.edu.my/socsscm

Ewww ewww ewww. 

Buy more RAM and things will run sooooooooooooooooo much quicker.

-- 
Darsant Silverstring 
<snip>



Alfred P. Reaud