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 <> 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:
> Search:
> Site:
Radiant mailing list

Reply via email to