Comments on: Do you like slow website ? http://www.camptocamp.com/en/blog/2009/09/do-you-like-slow-website/ Camptocamp weblog Fri, 10 Feb 2012 14:08:41 +0100 http://wordpress.org/?v=2.8.6 hourly 1 By: Jérôme Andrieux http://www.camptocamp.com/en/blog/2009/09/do-you-like-slow-website/cpage/1/#comment-2806 Jérôme Andrieux Mon, 21 Sep 2009 10:52:39 +0000 http://www.camptocamp.com/en/blog/2009/09/do-you-like-slow-website/#comment-2806 Among all possible optimizations, from page layout to system architecture, it's always nice to set up tools to measure performance.<br /><br />On the server side, I really like Munin (a linpro varnish project brother btw - http://munin.projects.linpro.no/) because of its lightness and all its nice plugins (<br />http://muninexchange.projects.linpro.no/)<br /><br />On the client side, I like to use Firebug with PageSpeed (http://code.google.com/speed/page-speed/) or yslow (http://developer.yahoo.com/yslow/).<br />Those tools provides a page level performance analysis and various recommendations.<br /><br />For web mapping sites, one could pay special attention to :<br />- serving static content with a dedicated service (from lighttpd, varnish, nginx+memcached to a CDN) - forget Squid<br />- reducing HTTP requests (CSS & JS minimizing is part of this) <br /><br />Pylons' performance is obviously sensible to load and scaling policy can require multiple load-balanced instances : http://pylonshq.com/docs/en/0.9.7/#internationalization-sessions-and-caching Among all possible optimizations, from page layout to system architecture, it's always nice to set up tools to measure performance.

On the server side, I really like Munin (a linpro varnish project brother btw – http://munin.projects.linpro.no/) because of its lightness and all its nice plugins (
http://muninexchange.projects.linpro.no/)

On the client side, I like to use Firebug with PageSpeed (http://code.google.com/speed/page-speed/) or yslow (http://developer.yahoo.com/yslow/).
Those tools provides a page level performance analysis and various recommendations.

For web mapping sites, one could pay special attention to :
- serving static content with a dedicated service (from lighttpd, varnish, nginx+memcached to a CDN) – forget Squid
- reducing HTTP requests (CSS & JS minimizing is part of this)

Pylons' performance is obviously sensible to load and scaling policy can require multiple load-balanced instances : http://pylonshq.com/docs/en/0.9.7/#internationalization-sessions-and-caching

]]>