We're comfortably running *three* production DSpace instances in a single Tomcat 6 with these limits:
JAVA_OPTS="-Xmx1024M -Xms768M" JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=128M" JAVA_OPTS="$JAVA_OPTS -XX:PermSize=32M" That's on a box with 3GB of physical memory. One DSpace instance is 1.6, and the other two are 1.5. Now, I do have an old weekly reminder to check PermGen on that box, but it is always around half filled these days. We had problems in the past, but newer versions of DSpace seem to do much better in that regard. I can't recall the last time we had to restart that Tomcat just to clean up memory. We have a development box with maybe two dozen DSpace instances, none of them very busy at all, various versions and states of disrepair, and we do have to restart Tomcat there from time to time if we are doing a lot of webapp. reloading. The limits there are: JAVA_OPTS="-Xmx1024M -Xms128M" JAVA_OPTS="$JAVA_OPTS -XX:PermSize=192M" JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=384M" on a 4GB machine. -- Mark H. Wood, Lead System Programmer [email protected] Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_
pgpDu2gzdSXuS.pgp
Description: PGP signature
------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
