JVM heap sizing for Java external task

TeamSite 6.5 SP2+
Solaris 2.9

We are launching a series of OD calls via a java external task in a workflow. We have a deployment for each of our 3 environments (each calling DataDeploy in standalone fashion).

Is there a best practice for picking a number to assign as the min and max heap size for our java external tasks? It seems that they are all defaulting to 77 MB, and I was thinking that this might be too much for some simple external tasks that are merely wrappers for calling opendeploy.

Aside from trial and error, I was wondering if anyone has some guidance to give.

Find more posts tagged with

Comments

ccprofessional

Is the default heap size used at startup of the java VM causing problems?
The beauty of Java is that we do not (usually) have to muck around heap size, garbage collection, etc. For what it's worth, if you are on TS 6.7.1, I think you will be using JVM 1.5 so the following changes to jvm 1.5 should apply:

http://java.sun.com/j2se/1.5.0/docs/guide/vm/gc-ergonomics.html