On Fri, Apr 26, 2013 at 10:11 AM, Aswini Rajasekaran
<[email protected]> wrote:
>
> Yes, the CPU usage of the process which runs hudson.war scales to 250+%.
Again, that only makes sense in the context of how many CPU's you have
- and whether they are real cores or hyperthreads that get counted as
CPUs. If you have 8 cores, 250% isn't all that busy.
> It doesn't run hudson.war alone, but it also runs the Maven, ANT, jboss and
> other tasks required by the jobs. And sometimes because of the intensity of
> the jobs or so, it goes out of PermGenSpace and I have to restart jenkins
> for resolving that. I run jenkins on a 32 bit server in Red Hat Linux.
That's something entirely different. You are short of RAM - and you
may be burning a lot of CPU in java garbage collection to deal with
it. Your real problem is that a 32 bit system will have a 2 GB
address space restriction even if the machine has more available.
> Can you tell me the good MAVEN_OPTS configuration settings? I think MAVEN
> runs out of memory when it does something with very high intensity and
> things break loose.
> I am not able to get the optimum MAVEN settings for Jenkins.
That's a battle I might have tried to fight in some other century, but
now the right answer is lots of RAM and a 64-bit OS and JVM.
--
Les Mikesell
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
