Warning: This page has not been updated in over over a year and may be outdated or deprecated.
administration:performance
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
administration:performance [2017/04/13 08:20] – [Further Reading] emaijala | administration:performance [2019/01/16 16:06] – [Apache Tuning] demiankatz | ||
---|---|---|---|
Line 138: | Line 138: | ||
from module directory. | from module directory. | ||
+ | ===== Asset Pipeline ===== | ||
+ | Starting with VuFind 3.1, there is an optional "asset pipeline" | ||
- | ===== Troubleshooting | + | ===== Theme Compiler |
- | There have been some reports of VuFind | + | Starting with VuFind |
- | // | + | To use a compiled theme, follow these steps: |
- | Inserting the line in index.php | + | |
- | // | + | |
- | < | + | 1. Run "php $VUFIND_HOME/public/ |
- | register_shutdown_function(' | + | |
- | </code> | + | |
- | // | + | 2. Update your [[configuration: |
- | immediately before requiring the session handler, seems to fix the problem with APC. Since this is the result | + | |
- | // | + | |
- | Note: As of VuFind 1.4, the default VuFind code will register | + | 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' | ||
====== Apache Tuning ====== | ====== Apache Tuning ====== | ||
- | For a productive environment, | + | |
+ | ===== GZIP Compression ===== | ||
+ | |||
+ | For a productive environment, | ||
<code bash> | <code bash> | ||
Line 169: | Line 172: | ||
</ | </ | ||
- | One thing you should also do is minifying JS and CSS files. This removes whitespaces and line breaks. It can by done by your IDE. Netbeans for example has a plugin Js CSS Minify Compress. The minified files must be configured in theme.config.php and in some cases in the theme files. Just search for " | + | Note that the " |
+ | |||
+ | ===== Minification ===== | ||
+ | |||
+ | One thing you should also do is minifying JS and CSS files. This removes whitespaces and line breaks. It can by done by your IDE. Netbeans for example has a plugin Js CSS Minify Compress. The minified files must be configured in theme.config.php and in some cases in the theme files. Just search for " | ||
+ | |||
+ | :!: Manual minification should not be necessary if you turn on VuFind' | ||
====== Solr Tuning ====== | ====== Solr Tuning ====== | ||
Line 238: | Line 247: | ||
See the [[configuration: | See the [[configuration: | ||
+ | ===== Limits ===== | ||
+ | |||
+ | Certain operating system limits can impact Solr performance, | ||
===== Further Reading ===== | ===== Further Reading ===== | ||
Line 248: | Line 260: | ||
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: | 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: | ||
- | |||
- | ====== Asset Pipeline ====== | ||
- | |||
- | Starting with VuFind 3.1, there is an optional "asset pipeline" | ||
====== Testing Performance ====== | ====== Testing Performance ====== |
administration/performance.txt · Last modified: 2022/05/06 12:52 by demiankatz