Hi, * Frode Petersen <fropeter@xxxxxxxxx> [2007-02-23 07:25]: > But I am using the Fedora version of Eclipse, which is a precompiled > version using the java stack included with Fedora, and since it is > precompiled, I don't have access directly to the java VM used, thus I > can't use a startup script as you suggested. This is incorrect. We build the bytecode exactly the same as upstream: with the JDT Core compiler, ecj. After the build is done - the exact same as upstream - we natively-compile all of the jars with gcj to shared libraries which can be used by gij. But you said you were running with the Sun VM so all you're using is the bytecode. /usr/bin/eclipse is the binary (native) launcher just like upstream that is used to spawn the VM. In the case of Sun, at least, the memory flags in the file I mention below should be respected. > Because of this there should be some means by which I could configure > the memory usage and possibly other things regarding that VM. I have > not as yet found any conclusive info on where that configuration is > done in the Fedora version of Eclipse. Or am I completely confused > here? You can fiddle with memory stuff (mx, etc.) in /usr/share/eclipse/eclipse.ini. It's the same as upstream except that it's owned by root and managed by RPM instead of just an exploded tarball :) . You may get some more tips if you ask on fedora-devel-java-list as some of the people there may have more experience with this kind of situation. One thing to confirm is that you are indeed running with the Sun VM. If you've downloaded plugins that aren't shipped with Fedora, they don't contain the gcj-compiled bits and if you're just running with our stock setup, they'll be purely interpreted by gij. They'll run slower than if there are .sos corresponding to the jars. But if you're running with the Sun VM then that's irrelevant. Andrew
Attachment:
pgpaj1XZvOJvV.pgp
Description: PGP signature
