| ExpiresDefault "access plus 1 week"
|
| </IfModule>
|
| FileETag none
|
| -{/code} The note "access plus 1 week" is quite arbitrary, some people recommend "access plus 1 year" or 2 years. This header can even be problematic! Its pros and cons are [http://developer.yahoo.net/blog/archives/2007/05/high_performanc_2.html|being discussed], as is [http://developer.yahoo.net/blog/archives/2007/07/high_performanc_11.html|the ETags setting].
|
| +{/code} The note "access plus 1 week" is quite arbitrary, some people recommend "access plus 1 year" or 2 years. This header can even be problematic! Its pros and cons are [http://developer.yahoo.net/blog/archives/2007/05/high_performanc_2.html|being discussed], as is [http://developer.yahoo.net/blog/archives/2007/07/high_performanc_11.html|the ETags setting]. Example: When I called mybitweaver/kernel/admin/index.php, YSlow gave me an F and reported |
| +{code title="before"}F (59), 207K, 52 HTTP Requests (Empty Cache), 52 HTTP Requests (Primed Cache){/code} |
| +After creating the above mentioned .htaccess file, I got a C! Only the actual HTML file and one JS file were downloaded again, the other files didn't cost an HTTP request anymore: |
| +{code title="after"}C (74), 207K, 52 HTTP Requests (Empty Cache), 2 HTTP Requests (Primed Cache){/code} |
|
|
| !! Template optimisation
|
| * To optimize your custom theme, read our ((Speed optimisation|Speed optimisation research)), comparing bitweaver to selected other content management systems by analyzing their main pages for HTTP requests and load times, and listing possibilities to optimize them.
|
|
|
| -!! Tools
|
| -* Install a PHP opcode caching mechanism. This might be the most notable performance boost of all! It will drastically reduce PHP memory usage and improve execution time, sometimes as much as several 100 percent! Recommendations are __[http://eaccelerator.net/HomeUk|php-eaccelerator]__ (a maintained version of [http://turck-mmcache.sourceforge.net/|turck-mmcache]) or __[http://php.net/apc|APC - 'Alternative PHP Cache']__.
|
| +!! Tools and information |
| +* Install a PHP opcode caching mechanism. This might be the most notable performance boost of all! It will drastically reduce PHP memory usage and improve execution time, sometimes as much as several 100 percent! Recommendations are |
| +** __[http://eaccelerator.net/HomeUk|php-eaccelerator]__ (a maintained version of [http://turck-mmcache.sourceforge.net/|turck-mmcache]); eAccelerator is detected or recommended by bitweaver's installer |
| +** __[http://xcache.lighttpd.net/|XCache]__, included in Ubuntu (successfully tested with bitweaver: Ubuntu 8, PHP 5, XCache 1.2.1) |
| +** __[http://php.net/apc|APC - 'Alternative PHP Cache']__ |
| * System Administration Tool: [http://www.vanheusden.com/multitail/|MultiTail] - tail on steroids
|
| * If you have a high traffic site, make sure you have an ((Advanced Apache Configuration for High Traffic Sites)).
|
| +* If you are running MySQL, there's this [http://www.ghastlyfop.com/blog/2008/01/lamp-performance-for-dummies.html|interesting page about MySQL tuning] |
| * If you have access to the configuration files of your web server and database, consider [http://docs.moodle.org/en/Performance|this performance guide], written for a well-known PHP software called Moodle. It lists all of the tricks mentioned here, as well as some in-depth recommendations on your server's hardware, its operating systems, Apache, IIS, MySQL and more, of which much applies also to bitweaver.
|
|
|
| !! PHP code optimization
|