nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Java Performance Tuning

delliott

We run 1,000+ deployments daily using the "iwodsched add" command and have experienced crashes of our base server, recently. Is anyone aware of any Java performance tuning we can do... increase heap size, etc. Version is OpenDeploy 5.6.0 SP1. Thanks.

Find more posts tagged with

Comments

Adam Stoller

Are you using the OOTB schedule DB or did you replace it with a "real" DB?
The OOTB DB is, I believe, *not* intended for production use.
I'm pretty sure this is covered in one of the manuals.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

delliott

Thanks for the reply.

We are using Oracle for the schedule db. We have also just begun using the "iwodcmd" command, rather than "iwodsched" to run our deployments as recommended by TechArticle #50057.

What I'm really looking for is if anyone has any guidelines on tweaking the Java settings... heap, garbage collection, etc., etc.

Our OD Base is 5.6.0 SP1 on SunOS 5.8.

jed

We constantly ran out of memory until we upped the heap size. Increasing the heap size, along with a weekly restart has helped us a lot. Our main issue was with dbLoader, so YMMV if you are not using dbLoader. Although, I suspect there are still memory leaks without dbLoader--just not as significant. On solaris, you do something like the following (we set ours to 1024):

vi +208 $odhome/processod
# -- for Solaris and Linux
JAVA_OPTS="-Xss2m -Xms32m -Xmx1024m"

Also, playing around with different garbage collection flags did not seem to do anything but increase (or decrease) the speed at which memory was collected. Once there is a leak, there is not much you can do about it.

Finally, on your dev box, you might want to add these flags:
-Xsqnopause -XX:+PrintClassHistogram -XX:+PrintGCDetails -verbose:gc

This will print verbose GC info into $odhome/od.log

--
Jed Michnowicz
jedm@sun.com
Content Management Engineering
Sun Microsystems

jed

I just noticed you are on 5.6. We are on 6.02 so, the exact file/line number may be different, but it should be a similar change to up the heap size.

--
Jed Michnowicz
jedm@sun.com
Content Management Engineering
Sun Microsystems