performance problems

Fri Aug 13 20:26:00 GMT 1999

Jeff Sturm wrote:
> > Shouldn't this be set on a per-application basis?
>> Maybe. We tend to tweak heap parameters in the field. Specifically for
> the JDK, we often adjust -ms and -mx on production sites. Gcj doesn't
> have a maximum heap, so it's not as important. Initial heap size is
> still a big win for memory-intensive programs with short run durations.

I actually hacked/implemented -ms and -mx in my local libgcj tree a while
back when I was playing around with the GC. I was just scanning the command
line arguments at runtime, calling the apropriate GC function with the
arguments, and removing the parameter from 'args' in order to avoid
conflicts with application code.
Some changes in the way gcj apps are initialized when the interpreter was
added broke it however, and I couldn't be bothered investigating so I
commented it out.
regards
 [ bryce ]