Thanks for the tips Charles, Sean, et al. Yeah, I saw mod_deflate in our
list of Apache modules, but ahem, I don't see any initialization code so
it's definitely on my todo list (as well as concat/minify JS, mod_expires,
etc.,etc.) However, I should mention that just setting the radiant cache to
24 hours alone has made a huge impact in perceived performance. So much so,
that I can probably punt for a few weeks on some of the other performance
related adjustments.

Of interesting note (for someone else who may be about to reset the cache)
it really seems that the default Radiant caching wasn't happening at all
(before I made the change). I'm inclined to say that this was somehow our
fault (wish I knew exactly why) and not Radiant's. That being said, after
making the appropriate changes to /config/environment.rb in the config after
init block (see older post in this thread for exact syntax details) it is
definitely "kicking in" and working great.

Of interest:
passenger will use the /config/environment.rb file's permissions to start
Rails instance(s) as this user, unless, the file is set to root, in which
case it will set the rails instance(s) to user nobody. This comes from the
Passenger docs. Who cares? Well, we had to chown the /tmp dir recursively to
user nobody (the directory that radiant uses to cache). Before doing so, we
had http 500 internal server errors. This is more a unix permissions thing
than a radiant thing, but it's in the context so I mention it as

On Sun, Jan 3, 2010 at 6:46 PM, Charles Roper <>wrote:

> On 29/12/2009 03:16, Rob Levin wrote:
> > Thanks all, you've given me a lot excellent information to work with and
> I
> > appreciate it!
> Rob,
> I've just run YSlow on your site and a suggestion it comes up with is to
> gzip your content:
> "Compression reduces response times by reducing the size of the HTTP
> response. Gzip is the most popular and effective compression method
> currently available and generally reduces the response size by about
> 70%. Approximately 90% of today's Internet traffic travels through
> browsers that claim to support gzip."
> You've got quite a lot of JS and CSS in there, so gzipping could work
> quite well.
> YSlow makes several other suggestions that could be worth looking into:
> I've used Heroku for Radiant sites and they employ Varnish, which seems
> to work exceedingly well for keeping things flying:
> Some further good stuff on caching, if you're interested:
> Charles
> _______________________________________________
> Radiant mailing list
> Post:
> Search:
> Site:
Radiant mailing list

Reply via email to