Are there any best JVM arguments for the JBE?
2 answers
Have you done any performance profiling of your build?
In my experience using the command line build definition, the only real work that the JBE's JVM is doing during my build is the source extract: the compilation & packaging activities are all performed via an external process. It seems to me that all of the build definitions would behave in the same way.
That's my long way of saying that I doubt there's much tweaking one can do on the JBE's JVM that would make much of a difference; you'd likely be better served looking at how the actual build JVM is configured.
In my experience using the command line build definition, the only real work that the JBE's JVM is doing during my build is the source extract: the compilation & packaging activities are all performed via an external process. It seems to me that all of the build definitions would behave in the same way.
That's my long way of saying that I doubt there's much tweaking one can do on the JBE's JVM that would make much of a difference; you'd likely be better served looking at how the actual build JVM is configured.
Comments
1 vote
1 vote
1 vote
showing 5 of 6
show 1 more comments
For the JBE process, we don't recommend any specific options for performance in general. I'd only consider tweaking them if you've identified a specific problem that needs addressing.
To help identify what's making your JBE build run slower than you expect, I'd first run and profile the different steps of your build from the command line so they don't involve JBE at all. This will help you see how much overhead JBE is adding to each step. Then you have some numbers to begin an investigation with.
To help identify what's making your JBE build run slower than you expect, I'd first run and profile the different steps of your build from the command line so they don't involve JBE at all. This will help you see how much overhead JBE is adding to each step. Then you have some numbers to begin an investigation with.