Mail Archives: djgpp/1993/12/13/11:16:23
> I have just installed djgpp 1.11 as a potential upgrade of Borland C++ V3.
> I expected its speed to be competitive, but it is much slower. (1/10?). At
> installation, I used no ramdrive or disk cache. There was a lot of disk
> activity. ramdrive.sys appeared to make little difference on its own to
> this. Using smartdrv.sys cut the disk activity to a negligible amount. (I
> have not tried smartdrv.sys without ramdrive.sys).
>
> Comments? Other's experience?
It is important to realize that the compiler in djgpp is *big*. The
files in the bin directory are stripped, so what you see is all code
and data, and must be read from the disk. Also, go32 must be loaded
for each binary.
I recommend a small ramdisk for gcc's temporary files (TEMP=) and at
least two meg of disk cache, plus at least one or two meg of
*available* memory for go32 to use. Running go32 gives you memory
availability information.
- Raw text -