[TYPO3-performance] mod_pagespeed anyone ?

[Georg Kuehnberger]

Dominique,
Thanks for sharing your experience and input.

On 22.11.2010 14:41, Dominique Feyer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I give it a small try, but the module use a lot of CPU ressource to
> parsing the request output ... so impossible to use it in production on
> a high load server.
> Maybe a configuration problem ...

I'd guess your config was too aggressive.

> but i think that this kind of
> configuration can be done in the Apache configuration without the need
> of this module (cache, header, expire, ...). For the other optimization
> (image processing, ...) ... the best way is to produce content correctly.

Fully agreed in regards to "do it right upfront".
However in quite some cases there is too little time to optimize 
html/css/js "upfront", due to everchanging requirements.

> I dont thinks that building image with script (imagemagick, ...) and
> after that optimizing on demand with a module like the google one is a
> good idea.

In case of TYPO3, the on-demand optimization by google's module for 
images is pretty much useless, as a well configured TYPO3 will do that 
one anyway.

> Optimization must be done before the client request not during.
ACK see above.

Having done some tests (by now) I feel mod_pagespeed is a fine tool to 
check which optimizations will improve page-weight and rendering-speed. 
 From there onwards we would pick the important pieces (80/20) for 
manual optimization and eventually leave the rest to mod_pagespeed.

regards georg

PS: The fact that one of the largest hosters in the US, go-daddy, 
considers to use mod_pagespeed on all of its client-servers at least 
tells us that there's a huge oppertunity to save bandwidth and improove 
user-experience. (No, non of our clients are hosting there ;-)


> ++
>
> Dominique Feyer
>
> Georg Kuehnberger wrote:
>> Hi,
>>
>> Did anmyone of you testdrive the new Google Apache module called
>> mod_pagespeed with TYPO3?
>> It's supposed to ease the process of performance-tuning your HTML/CSS/JS
>> (and even images) via some magic and thus speed-up your site by quite
>> some percentage. For more details see below;
>>
>> reards georg
>>
>>
>> pagespeed
>>
>> mod_pagespeed is an open-source Apache module that automatically
>> optimizes web pages and resources on them. It does this by rewriting the
>> resources using filters that implement web performance best practices.
>> Webmasters and web developers can use mod_pagespeed to improve the
>> performance of their web pages when serving content with the Apache HTTP
>> Server.
>>
>> mod_pagespeed includes several filter that optimize JavaScript, HTML and
>> CSS stylesheets. It also includes filters for optimizing JPEG and PNG
>> images. The filters are based on a set of best practices known to
>> enhance web page performance. Webmasters who set up mod_pagespeed in
>> addition to configuring proper caching and compression on their Apache
>> distribution should expect to see an improvement in the loading time of
>> the pages on their websites.
>>
>> from: http://code.google.com/speed/page-speed/docs/module.html
>>
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.16 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJM6nL9AAoJEOb2VUSS7rJYk2kH/0ouimSdLdKCZDbh0a89a4s9
> bP5hw+ZE6vrzluv0533mPmSAqQa/SrB2SJ4JldlQGzdj3z3uN8t7/2Zhx1Rc8in2
> +Pa3ROnLhUrqClysaZdQNG4diyw+m+U0VkTclCo8kTr/sfgvKEXkMBfgUcqi+gku
> M6LrmrdKe9VXEwJv98lsP4otn9PQsdKr5rMW+9xK2j2CVviuqjoGukW/qOZcPzrR
> yOdNBI4iH5Q2K37OYM7S6NdHmkPo438b1zqE0ll1eWRAqDFqkkxcl+s1eXovIka8
> SbYAV95VSPgXFsBBnhPJsDiX9GWtc9R5dDv4tFlKMDAUpKJy7RVVhggyKhm/0u4=
> =Fq4U
> -----END PGP SIGNATURE-----