>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
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.
> 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:
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>
> >> I've just started working at a place that is using Radiant for it's web
> >> and I've noticed our general pages are usually somewhere around 150kb
> >> 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"
> >> 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
> >> ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby
> >> Edition 20090610. We have our own dev server but for production we're
> >> server beach.
> >> Looking at our Radiant instance's /config/environment.rb file I noticed
> >> 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
> >> sizes, what Radiant specific stuff can I do to speed things up? Even
> >> 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