litvinovg/vivo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Adding information about setting the limits.conf file to improve performance.

Browse source
This commit is contained in:
ejc12 2010-10-18 15:12:26 +00:00
parent 8789f269fc
commit fba4e40549
1 changed files with 11 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

14
doc/install.txt
View file

@ -27,13 +27,13 @@ are slightly different. Please consult developers.txt in this directory.
* III. Download the VIVO Application Source * III. Download the VIVO Application Source
* IV. Specify deployment properties * IV. Specify deployment properties
* V. Compile and deploy * V. Compile and deploy
* VI. Set Tomcat JVM Parameters * VI. Set Tomcat JVM parameters and security limits
* VII. Start Tomcat * VII. Start Tomcat
* VIII. Log in and add RDF data * VIII. Log in and add RDF data
* IX. Set the Contact Email Address (if using "Contact Us" form) * IX. Set the Contact Email Address (if using "Contact Us" form)
* X. Setup Apache Tomcat Connector * X. Setup Apache Tomcat Connector
* XI. Configure Pellet Reasoner * XI. Configure Pellet Reasoner
* XII. Was the Installation Successful? * XII. Was the installation successful?
------------------------------------------------------------------------------- -------------------------------------------------------------------------------
@ -169,7 +169,7 @@ to build VIVO and deploy to Tomcat's webapps directory.
------------------------------------------------------------------------------- -------------------------------------------------------------------------------
VI. Set Tomcat JVM Parameters VI. Set Tomcat JVM parameters and security limits
Currently, VIVO copies the contents of your RDF database into memory in order Currently, VIVO copies the contents of your RDF database into memory in order
to serve Web requests quickly (the in-memory copy and the underlying database to serve Web requests quickly (the in-memory copy and the underlying database
@ -192,6 +192,14 @@ sets of data, 256m to 512m should be sufficient.
If an OutOfMemoryError is encountered during VIVO execution, it can be remedied If an OutOfMemoryError is encountered during VIVO execution, it can be remedied
by increasing the heap parameters and restarting Tomcat. by increasing the heap parameters and restarting Tomcat.
Security limits: VIVO is a multithreaded web application that may require more threads than are
permitted under your Linux installation's default configuration. Ensure that
your installation can support the required number of threads by making the
following edits to /etc/security/limits.conf:
apache hard nproc 400
tomcat6 hard nproc 1500
------------------------------------------------------------------------------- -------------------------------------------------------------------------------
VII. Start Tomcat VII. Start Tomcat