Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The software DSpace relies on does not come out of the box optimized for large repositories. Here are some tips to make it all run faster.

Give Tomcat More Memory

Performance tuning in Java basically boils down to memory. Tomcat is especially memory hungry, and will benefit from being given lots of RAM. To set the amount of memory available to tomcat edit `$TOMCAT_HOME/bin/setclasspath.sh` and append a line like: -

JAVA_OPTS=-Xmx512m -Xms512m

If the machine is dedicated to DSpace a decent rule of thumb is to give tomcat half of the memory on your machine. The latest guidance from Sun is to set -Xms to the same value as -Xmx for server applications such as tomcat.

Give the Command Line Tools More Memory

Edit the `-Xmx` argument on the last line of `$DSPACE_HOME/bin/dsrun` to increase the memory available to command line tools. Especially useful for big batch jobs.

Give PostgreSQL More Memory

On many linux distros PostgreSQL comes out of the box with an incredibly conservative configuration - it uses only 8Mb of memory! To put some more fire in its belly edit the `shared_buffers` parameter in `postgresql.conf`. The memory usage is 8KB multiplied by this value. The advice in the postgres docs is not to increase it above 1/3 of the memory on your machine.

JHU Analysis of Ingest DB Activity

JhuIngestDbAnalysis

  • No labels