Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
administration:performance [2016/09/13 19:16] – [PHP Tuning] demiankatz | administration:performance [2018/03/22 13:53] – [Theme Compiler] emaijala |
---|
</code> | </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! |
| |
| |
from module directory. | from module directory. |
| |
| ===== 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]]. |
| |
| ===== Theme Compiler ===== |
| |
| Starting with VuFind 4.1, there is a [[administration:command_line_utilities|command-line tool]] known as the "theme compiler" which can be run to flatten a hierarchy of themes into a single flat theme, reducing the amount of file searching VuFind needs to do in order to find assets and templates. |
| |
| To use a compiled theme, follow these steps: |
| |
| 1. Run "php $VUFIND_HOME/public/index.php compile theme [your theme] [your compiled theme]" at the command line. |
| |
| 2. Update your [[configuration:files:config.ini|config.ini]] file to use [your compiled theme] instead of [your theme] in the theme setting. |
| |
| Note: NEVER EDIT THE COMPILED THEME. Instead, edit the source theme and recompile it when you need to make changes. You must use the --force switch of the compiler if you need to overwrite your compiled theme with a new version. |
| |
| ===== Session Handling ===== |
| |
| When using database sessions, deleting expired sessions may be a surprisingly heavy process. On a busy site it may be beneficial to turn off PHP's session garbage collection (set session.gc_probability to 0 in php.ini) and run VuFind's expire_sessions utility regularly. This makes sure that garbage collection is done outside Apache that serves user requests and with a method that makes it possible to handle session deletion in a large table. |
===== Troubleshooting ===== | ===== Troubleshooting ===== |
| |
| |
* [[administration:solr_replication|Solr Replication]] - Basic information about making Solr highly available with replication in the context of VuFind. | * [[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://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. | * [[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. |