Concerning the setting the timeout link: http://groups.google.com/group/radiantcms/msg/01ac040dbcf76479
I thought I should add (in case someone is following this thread that needs to do this) that you have to put it in the callback block for after radiant has finished it's initialization (at the end of the config/environment.rb file): config.after_initialize do # Timeout cache every 24 hours SiteController.cache_timeout = 24.hours After adding ran script/console to confirm: >> SiteController.cache_timeout 86400 seconds Also using page speed in addition to yslow. Not yet doing the compression/minification but that's on the todo list. Thanks all for the wonderful suggestions yesterday! Rob > > > 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 > _______________________________________________ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
