I was just wondering, whether techniques do people use to tune the performance of an Umbraco based site? I know you can set macros to cache, and some people have had speed improvements by monitoring the DB calls and adding indexes. But what are the "must does" to optimise a sites performance?
It's probably the same old rules for any site or program... be careful in your programming (macros, dlls, extensions, event handlers). I use the ?umbDebugShowTrace=true querystring parameter when developing a site to see where the site is slow and then re-work those items for better performance. Only at the very last step before going live do I enable macro caching as that can hide a performance problem with it's outstanding performance gains.
Beyond that, the usual rules for websites of expires headers, a CDN, serve images and static files from another domain, compress and concatinate all html, css, and js files (PeterD Compression!), use CSS sprites, watch your filesize, etc. etc. Tools like firebug, yslow, and others can help you find such issues.
Tips for peformance tuning?
Hi Guys,
I was just wondering, whether techniques do people use to tune the performance of an Umbraco based site? I know you can set macros to cache, and some people have had speed improvements by monitoring the DB calls and adding indexes. But what are the "must does" to optimise a sites performance?
Many thanks
Matt
Hi,
Checkout the folowing pages:
http://umbraco.org/blog/2007/12/14/dec-10-dramatic-performance-increase-in-two-minutes
http://www.shrinkrays.net/articles/umbraco-hacks.aspx
Ron
It's probably the same old rules for any site or program... be careful in your programming (macros, dlls, extensions, event handlers). I use the ?umbDebugShowTrace=true querystring parameter when developing a site to see where the site is slow and then re-work those items for better performance. Only at the very last step before going live do I enable macro caching as that can hide a performance problem with it's outstanding performance gains.
Beyond that, the usual rules for websites of expires headers, a CDN, serve images and static files from another domain, compress and concatinate all html, css, and js files (PeterD Compression!), use CSS sprites, watch your filesize, etc. etc. Tools like firebug, yslow, and others can help you find such issues.
cheers,
doug.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.