Go to content Go to menu

We recently upgraded MOspace to DSpace 3.1 . I’ll be talking about this in a talk I’m giving at Open Repositories 2013 . But I did want to mention right here that today I had to re-tweak our Tomcat settings, mostly to increase the Java heap memory allocation. I’ve revised the DSpace documentation to increase the recommendations, based on this experience. But, for those in a hurry, here are the JAVA_OPTS I use in production (and a big shout-out to Mark Wood in Indiana, who has always helped me find the best settings for my repository, I’d be lost without you, Mark, thanks!):

JAVA_OPTS="-Xmx1536M -Xms256M"
JAVA_OPTS="${JAVA_OPTS} -XX:MaxPermSize=192M"
JAVA_OPTS="${JAVA_OPTS} -XX:PermSize=96M"

# tweak from Bill Anderson at GAtech: use the parallel garbage collector
JAVA_OPTS="$JAVA_OPTS -XX:+UseParallelGC"

# turn on UTF-8 encoding for URLs
JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=UTF-8"

# turn on jmxremote so LambaProbe can work
JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote"

# turn on the Yourkit profiler
JAVA_OPTS="$JAVA_OPTS -agentpath:/usr/local/yourkit/bin/linux-x86-32/libyjpagent.so=delay=10000"

# stop hiding stack traces, we need them! (see DS-1174 for why)
JAVA_OPTS="$JAVA_OPTS -XX:-OmitStackTraceInFastThrow"