Bryce McKinlay <[EMAIL PROTECTED]> writes:
> "Ian D. Stewart" wrote:
>
> > Processor: 75MHz Pentium
> > Memory: 16 MB Physical; 64 MB swap
> > Hard Drive: 1.2 GB WD Caviar w/ ~150 MB free
> >
> > By compiling each class individually, the compiler compiles that single
> > class, along with any immediate dependencies, then stops, releasing
> > allocating resources. This results in a both a much cleaner and faster
> > (or, in my case, achievable) build process.
>
> I can see how it could cause problems on small systems, however. Perhaps
> building package-at-a-time, rather than the entire project, would be a good
> compromise?
There are way too many cross package dependencies for that to work
effectively. I can try setting up my dependency file and compiling
with javac/jikes in that manner to see if that reduce the system
resources required. I do know that with jikes currently you'd
probably want around 64M of RAM to compile everything. I previously
had just 64M of RAM and 128M of swap. The jikes group is working to
make sure jikes isn't leaking memory and any fixes in that area should
reduce the memory footprint. Your CPU speed should be fairly
irrevolent... it will just make things slower. I don't know what else
you're using at the time on this machine... but you could try not
running X at the same time you compile given how tight your resources
are. You could also look for unused kernel modules sucking up lots of
memory like the nfs one sometimes does.
Brian
--
Brian Jones <[EMAIL PROTECTED]>
