[Radiant] How to improve site performance?
I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
Rob Levin wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! Are you trying to reduce the 150KB or the 800ms? If you're after the size, you'll need to look at the content more closely - there are probably stylesheets and JS files that are larger. You may need to minify them - I think the SnS extension (or one of its cousins) does that: http://ext.radiantcms.org/extensions/53-sns If you're after the time, I'm not sure where the time is going - you will probably need to see the logs to see where the time is being spent. Are you using many extensions? Are your pages being populated as a result of many queries (database and/ or HTTP)? Finally, you can change the page caching time to a much larger value compared to the default 5 minutes if your pages can manage it. Remember that a page you edit will be expired from cache when you edit it and all pages are expired from cache when the site basics (snippets, layouts, etc.) are changed [if I remember correctly]. Lastly, others may be able to help a bit more if you point us to the website :D Cheers, Mohit. 12/29/2009 | 8:41 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
Mohit Sindhwani wrote: Rob Levin wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! Are you trying to reduce the 150KB or the 800ms? If you're after the size, you'll need to look at the content more closely - there are probably stylesheets and JS files that are larger. You may need to minify them - I think the SnS extension (or one of its cousins) does that: http://ext.radiantcms.org/extensions/53-sns If you're after the time, I'm not sure where the time is going - you will probably need to see the logs to see where the time is being spent. Are you using many extensions? Are your pages being populated as a result of many queries (database and/ or HTTP)? Finally, you can change the page caching time to a much larger value compared to the default 5 minutes if your pages can manage it. Remember that a page you edit will be expired from cache when you edit it and all pages are expired from cache when the site basics (snippets, layouts, etc.) are changed [if I remember correctly]. Lastly, others may be able to help a bit more if you point us to the website :D ... and I think it's good practice to have your style sheets not stored in the database, save them to the file system directly so that there is no overhead every time a style sheet is requested - but that is a tradeoff between simplicity (you/ your designer can edit it directly through the Radiant interface) and performance (no Radiant involved in serving it up, straight from Apache). Cheers, Mohit. 12/29/2009 | 8:48 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
some things that come to mind immediately: - make sure you are not serving css and/or js from radiant - make sure you have mod_deflate setup up to compress all text files - avoid excessive use of page parts - avoid using paperclipped or page_attachments for design assets (like your logo or icons or things that don't need to be managed by your content editors) On Mon, Dec 28, 2009 at 6:20 PM, Rob Levin roblevinten...@gmail.com wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
oh and i'd think 300-400ms or less spent inside the rails process would be sufficient for all but the most performance critical applications since your web server should be able to serve the rest of your page (static assets, css, js) in less than 100ms On Mon, Dec 28, 2009 at 6:49 PM, john muhl johnm...@gmail.com wrote: some things that come to mind immediately: - make sure you are not serving css and/or js from radiant - make sure you have mod_deflate setup up to compress all text files - avoid excessive use of page parts - avoid using paperclipped or page_attachments for design assets (like your logo or icons or things that don't need to be managed by your content editors) On Mon, Dec 28, 2009 at 6:20 PM, Rob Levin roblevinten...@gmail.com wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
Mohit: Are you trying to reduce the 150KB or the 800ms? I assume we're going to hopefully improve by reducing the 150kb but I'd still like to proportionally decrease the load time if at all possible. change the page caching time to a much larger value compared to the default 5 minutes if your pages can manage it. Yes, I'm looking in to this. I'm almost positive we're just using the default. I agree that this may help a LOT! Does someone have a working example of setting: ResponseCache.defaults[:expire_time] or whatever? That would be very helpful. John Mohit: make sure you are not serving css and/or js from radiant I have my styles and js in RADIANT_ROOT/public/stylesheet /javascripts respectively. Is that correct? It's my understanding that Apache will serve anything under /public right? make sure you have mod_deflate setup up to compress all text files Yeah, I need to look into this! I do see it listed mod_deflate.so in our modules directory but I have to see if it's been properly loaded, etc. Thanks. page parts Well we are using layouts, snippets, parts, etc., pretty heavily. Is this specific to page parts or are snippets, layouts, etc., also hot spots? Here's the live site: http://www.snaplogic.com/ Thanks for the great help all! On Mon, Dec 28, 2009 at 4:54 PM, john muhl johnm...@gmail.com wrote: oh and i'd think 300-400ms or less spent inside the rails process would be sufficient for all but the most performance critical applications since your web server should be able to serve the rest of your page (static assets, css, js) in less than 100ms On Mon, Dec 28, 2009 at 6:49 PM, john muhl johnm...@gmail.com wrote: some things that come to mind immediately: - make sure you are not serving css and/or js from radiant - make sure you have mod_deflate setup up to compress all text files - avoid excessive use of page parts - avoid using paperclipped or page_attachments for design assets (like your logo or icons or things that don't need to be managed by your content editors) On Mon, Dec 28, 2009 at 6:20 PM, Rob Levin roblevinten...@gmail.com wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
On Mon, Dec 28, 2009 at 7:13 PM, Rob Levin roblevinten...@gmail.com wrote: change the page caching time to a much larger value compared to the default 5 minutes if your pages can manage it. Yes, I'm looking in to this. I'm almost positive we're just using the default. I agree that this may help a LOT! Does someone have a working example of setting: ResponseCache.defaults[:expire_time] or whatever? That would be very helpful. http://groups.google.com/group/radiantcms/msg/01ac040dbcf76479 John Mohit: make sure you are not serving css and/or js from radiant I have my styles and js in RADIANT_ROOT/public/stylesheet /javascripts respectively. Is that correct? It's my understanding that Apache will serve anything under /public right? that's right page parts Well we are using layouts, snippets, parts, etc., pretty heavily. Is this specific to page parts or are snippets, layouts, etc., also hot spots? they require additional database access. however if your database is properly tuned it's generally not much of an issue. it's just something i've noticed on the few apps i track with new relic rpm; in nearly all of them PagePart#find is the most time consuming transaction except in apps that use paperclipped and in that case Asset#find is the slowest. Here's the live site: http://www.snaplogic.com/ the x-runtime header (for the homepage) says 457ms (which is a pretty insignificant part of your total response time) is spent in the rails process so you're likely going to get much more bang for your buck by starting with generic optimizations rather that digging too deeply into radiant (e.g. reducing use of snippets or page parts). a tool like the yslow addon for firefox might help get you started: https://addons.mozilla.org/en-US/firefox/addon/5369. Thanks for the great help all! On Mon, Dec 28, 2009 at 4:54 PM, john muhl johnm...@gmail.com wrote: oh and i'd think 300-400ms or less spent inside the rails process would be sufficient for all but the most performance critical applications since your web server should be able to serve the rest of your page (static assets, css, js) in less than 100ms On Mon, Dec 28, 2009 at 6:49 PM, john muhl johnm...@gmail.com wrote: some things that come to mind immediately: - make sure you are not serving css and/or js from radiant - make sure you have mod_deflate setup up to compress all text files - avoid excessive use of page parts - avoid using paperclipped or page_attachments for design assets (like your logo or icons or things that don't need to be managed by your content editors) On Mon, Dec 28, 2009 at 6:20 PM, Rob Levin roblevinten...@gmail.com wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
Rob, Looking at http://www.snaplogic.com/ the first and biggest thing I would suggest would be to combine your 7 (not including ga_tracker) .js files into one. You could also look into using the google hosted versions of jquery and mootools. -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
Hey Rob - Also think about combining whatever (non-repeating background) images you have into one sprite file, combining CSS and JS files into one file, for each respectively. You're going to see a big hit in perceived speed if you're making that many requests to your web server. Do a fresh request to your site while looking at the Net tab in firebug and you'll see what I mean. - Joel On Mon, Dec 28, 2009 at 9:23 PM, Arthur Gunn art...@gunn.co.nz wrote: Rob, Looking at http://www.snaplogic.com/ the first and biggest thing I would suggest would be to combine your 7 (not including ga_tracker) .js files into one. You could also look into using the google hosted versions of jquery and mootools. -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Is it possible to exclude certain pages from being indexed by sphinx_search?
I did not see a clear way to do this and I have some pages that are not appropriate to show up. Is there a way without hacking a negation regex into the source? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Is it possible to exclude certain pages from being indexed by sphinx_search?
Hi Rob, I believe that on each page, clicking the more link under the title will reveal an option to not have that page searchable. -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Is it possible to exclude certain pages from being indexed by sphinx_search?
Thanks. Don't know how I missed that ;) On Mon, Dec 28, 2009 at 7:20 PM, Arthur Gunn art...@gunn.co.nz wrote: Hi Rob, I believe that on each page, clicking the more link under the title will reveal an option to not have that page searchable. -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant Digest, Vol 45, Issue 28
Rob, In addition to the other comments, the use of Google's FireFox plugin, Page Speed, for tuning up the front-end code would help with reducing load time. Best regards, -Bill On Dec 28, 2009, at 6:17 PM, radiant-requ...@radiantcms.org wrote: So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
