Hi all,

Interesting thread so far and keep up the good discussion.

I think it'd be helpful to us all if we could all share more information 
about our DSpace setups (similar to Mark Wood's tip on his local 
JAVA_OPTS settings).  The more we know about your 
DSpace/Java/Tomcat/Postgres (or Oracle) configurations, server setups, 
etc. the better chance we have at helping you out. There may be some 
immediate performance improvements you can achieve just by tweaking your 
setup/configurations slightly.

I had setup a basic template for this on the Wiki at 
https://wiki.duraspace.org/display/DSPACE/ScalabilityIssues1.6
But, feel free to just send info along in any format you wish.  The 
template was mostly there to give everyone an idea of what type of 
information can be useful to us (so that we can hopefully provide you 
with some helpful suggestions and find longer term fixes).

Obviously, we also want to track down and fix any memory leaks or larger 
problems as well.  So if you've already discovered specific issues, let 
us know about those as well, so we can add them to our Issue Tracker 
(http://jira.dspace.org/) and schedule them to be resolved.

Thanks,

Tim Donohue
Technical Lead for DSpace Project
DuraSpace.org

On 9/29/2010 7:59 AM, Mark H. Wood wrote:
> 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.
>
>
>
>
> ------------------------------------------------------------------------------
> 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

------------------------------------------------------------------------------
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

Reply via email to