@@ -19,7 +19,7 @@ |
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] [http://essaywritingservices.org/book-report.php|online book reports]. Example: When I called mybitweaver/kernel/admin/index.php, YSlow gave me an F and reported
|
+{/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}
|
|
|
@@ -35,7 +35,7 @@ |
* 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://cvresumewriters.com/onlineresume.php|certified resume writers] [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.
|
+* 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
|
* Use [http://www.php.lt/benchmark/phpbench.php|Fast Coding Habits].
|
|
|