Differences

This shows you the differences between two versions of the page.

--- administration:performance [2016/05/13 19:40] – [Heap Space] demiankatz
+++ administration:performance [2017/04/13 08:20] – [Further Reading] emaijala
@@ Line 44: / Line 44: @@
 for more information).
 ==== Garbage Collection ====
+:!: Starting with VuFind 3.0, VuFind includes Solr 5, which does some garbage collection auto-tuning by default; the suggestions below may be less important for these newer releases, and you should probably not tinker with settings unless you have a known problem you are trying to solve.
 Garbage collection is how aggressive the JVM is with clearing out unneeded objects. For the purposes of Vufind, parallel garbage collection should work nicely, but read Sun's [[http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html | Tuning Garbage Collection]] for more in-depth information.
@@ Line 67: / Line 69: @@
 </code>
-Once you have a log file, you can use the [[http://www.tagtraum.com/gcviewer.html|gcviewer]] or [[http://www.alphaworks.ibm.com/tech/pmat|PMAT]] tool to get a visual representation of its contents.  This is very helpful in measuring whether your configuration changes have had a positive impact!
+Once you have a log file, you can use the [[https://github.com/chewiebug/GCViewer|gcviewer]] or [[http://www.alphaworks.ibm.com/tech/pmat|PMAT]] tool to get a visual representation of its contents.  This is very helpful in measuring whether your configuration changes have had a positive impact!
@@ Line 130: / Line 132: @@
 On PHP 5.4, installing a PHP cache like [[http://pecl.php.net/package/APC|APC]] can significantly improve performance by reducing the amount of time spent by PHP parsing and compiling code. PHP 5.6 comes with build-In OpCache, which is slightly faster than APC. When upgrading, remember to disable the Apache APC module. OpCache should be configured to 64 MB.
-If you created a custom module, remember to create a autoloader_classmap.php by calling
+If you created a custom module, remember to create an autoloader_classmap.php by calling
 <code php>
 ../../vendor/zendframework/zendframework/bin/classmap_generator.php -w
@@ Line 239: / Line 241: @@
   * [[administration:solr_replication|Solr Replication]] - Basic information about making Solr highly available with replication in the context of VuFind.
+  * [[administration:fault_tolerance_and_load_balancing|Fault Tolerance and Load Balancing]] - Fault tolerance and load balancing strategies with VuFind.
   * [[http://wiki.apache.org/solr/SolrPerformanceFactors|Solr Wiki - Performance Factors]] - Pros and cons of various Solr configuration options; also linked to other helpful wiki pages.
   * [[http://groups.google.com/group/solrmarc-tech/browse_thread/thread/fe329385bb1dc953|solrmarc-tech indexing time thread]] - A discussion which goes into detail on several significant Solr settings.
@@ Line 245: / Line 248: @@
 Search engine crawlers can sometimes put a heavy load on your server, causing performance issues for actual users. The behavior of search engine robots can be controlled with the help of a [[administration:robots.txt]] file. See the [[administration:robots.txt]] page for more details.
+====== Asset Pipeline ======
+Starting with VuFind 3.1, there is an optional "asset pipeline" which can be used to combine Javascript and/or CSS files together to reduce the number of HTTP requests necessary to load VuFind pages. This is turned off by default but can be activated using the asset_pipeline setting in [[configuration:files:config.ini|config.ini]].
 ====== Testing Performance ======