[Radiant] Radiant performance
Hi all,
I've set up my new website http://software-consultant.net/ using Radiant 0.8.1
and a bunch of extensions. In particular, I use
* Archive
* Feed-Reader
* Markdown
* Blog
* Nested layouts
* Paperclipped attachments
* Reorder
* Tags
* Thinking-Sphinx search
* Navigation tags
* Sitemap
* Filesystem Import/Export
For production, the site is running on a dual-core AMD server, 6GB RAM with a
hardware RAID-1 under 64bit Ubuntu 8.0.4 LTS - pretty decent hosting for what
is basically a low-profile site. However, it takes Apache2/Passenger several
seconds (~2 seconds, sometimes up to 3) to fully render a page, and from the
rails logs I assume that it's not Apache being responsible for the delay. From
the current log:
Processing SiteController#show_page (for 109.90.135.63 at 2010-01-04
08:58:57) [GET]
Parameters: {action=show_page, url=[projekte,
redesign-webdynpro-java], controller=site}
Completed in 1792ms (DB: 40) | 200
[http://software-consultant.net/projekte/redesign-webdynpro-java/]
My layout consists of a master template, a page template for most of the
stuff and a project template inside page for URLs like the one mentioned
above. No recursion involved. I've got ~50 pages and 8 snippets.
I suspect feedreader to connect to the RSS source for every request, which I
will look into next. Removing the feedreader snippet from the layout doesn't
show much improvement though, so what's taking Radiant so long?
I've got other rails applications on the very same setup that act quickly, so I
guess it's not a general problem with my installation. Any comments? Your help
is appreciated very much. Kind regards,
Christian
___
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 performance
You might check out Rack::Bug to get an idea why the rendering time is
that high:
http://github.com/brynary/rack-bug
Best regards
Stefan
On 04.01.2010, at 09:06, Christian Aust wrote:
Hi all,
I've set up my new website http://software-consultant.net/ using
Radiant 0.8.1 and a bunch of extensions. In particular, I use
* Archive
* Feed-Reader
* Markdown
* Blog
* Nested layouts
* Paperclipped attachments
* Reorder
* Tags
* Thinking-Sphinx search
* Navigation tags
* Sitemap
* Filesystem Import/Export
For production, the site is running on a dual-core AMD server, 6GB
RAM with a hardware RAID-1 under 64bit Ubuntu 8.0.4 LTS - pretty
decent hosting for what is basically a low-profile site. However, it
takes Apache2/Passenger several seconds (~2 seconds, sometimes up to
3) to fully render a page, and from the rails logs I assume that
it's not Apache being responsible for the delay. From the current log:
Processing SiteController#show_page (for 109.90.135.63 at
2010-01-04 08:58:57) [GET]
Parameters: {action=show_page, url=[projekte, redesign-
webdynpro-java], controller=site}
Completed in 1792ms (DB: 40) | 200
[http://software-consultant.net/projekte/redesign-webdynpro-java/
]
My layout consists of a master template, a page template for most
of the stuff and a project template inside page for URLs like
the one mentioned above. No recursion involved. I've got ~50 pages
and 8 snippets.
I suspect feedreader to connect to the RSS source for every request,
which I will look into next. Removing the feedreader snippet from
the layout doesn't show much improvement though, so what's taking
Radiant so long?
I've got other rails applications on the very same setup that act
quickly, so I guess it's not a general problem with my installation.
Any comments? Your help is appreciated very much. Kind regards,
Christian
___
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?
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 forewarning. On Sun, Jan 3, 2010 at 6:46 PM, Charles Roper reac...@charlesroper.co.ukwrote: 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: https://addons.mozilla.org/en-US/firefox/addon/5369 I've used Heroku for Radiant sites and they employ Varnish, which seems to work exceedingly well for keeping things flying: http://docs.heroku.com/http-caching http://varnish.projects.linpro.no/ Some further good stuff on caching, if you're interested: http://tomayko.com/writings/things-caches-do http://www.mnot.net/cache_docs/ Charles ___ 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?
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 forewarning. I usually set up an instance as a neutral deploy user, or chown the whole deployment tree to the www-data user (Apache). Although it's slightly harder to execute arbitrary code in a Rails app than a typical PHP app, it's still smart to sandbox when possible. Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] time now
I don't know how good of a fix this is but it seemed to help my situation. On the date tag I changed Time.now to Time.zone.now Steven On Jan 2, 2010, at 7:48 PM, Steven Southard wrote: I added it to the issues on github. If anyone knows how to solve this or a handy work-around it would be much appreciated. Best, Steven On Dec 31, 2009, at 4:02 PM, Jim Gay wrote: Not sure how to solve it, but I want to push out a 0.8.2 release to solve problems with developers running rake tasks with newer versions of cucumber installed. Please create an issue for it. On Dec 31, 2009, at 12:02 PM, Steven Southard wrote: Oh, well okay. I'm working with 0.8.1 I tried looking on github for this bug but I don't even see them being tracked for versions older then 0.9.0. Anyone know how to solve this? Steven On Dec 31, 2009, at 8:27 AM, Sean Cribbs wrote: Steven, That is actually a bug. All emitted times should be in the chosen time zone. Sean On 12/30/09 9:54 PM, Steven Southard wrote: I have time set for Mountain time so all of my pages are saved as that time but if I ask for r:date for='now' / to compare with the page save date it gives me the server's time which is set for GMT. Is there a way to ask for Radiant's time now or local time? ___ 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] Port number.....
Installation of Radiant sets port 8080. How do I change this port number? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] summarize
What happened to you? You're still listed in the extension registry but the link is missing on github. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Port number.....
radiant does not set any port number. it is set by your application server (mongrel, thin, unicorn etc.). On Mon, Jan 4, 2010 at 2:29 PM, David Passmore d...@psu.edu wrote: Installation of Radiant sets port 8080. How do I change this port number? ___ 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] summarize
Thanks John. I tried searching github but sometimes the search is weird there. Someone should update the extension registry because it has the wrong link. On Jan 4, 2010, at 5:58 PM, john muhl wrote: what about http://github.com/atinypixel/radiant-summarize-extension ? On Mon, Jan 4, 2010 at 4:30 PM, Steven Southard ste...@stevensouthard.com wrote: What happened to you? You're still listed in the extension registry but the link is missing on github. ___ 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] radiant::cache, nginx and :use_x_accel_redirect
today i had go at upgrading a 0.6.9 app (which used a very old patch
to make x-accel-redirect work with radiant's ResponseCache) to 0.8.1
and ran into (what i'm guessing is) an issue with radiant::cache,
:use_x_accel_redirect option and firefox. under the following
conditions firefox will receive a response with an
application/octet-stream content-type header and prompts me to save an
untyped data file.
1. rm -rf tmp/cache/*/*
2. load a page in firefox
3. verify entity and meta cache entries were created
4. reload the page
- 304 not modified response
- see the custom X-Accel-Redirect header i set in nginx
- see all the headers set by radiant
5. edit and save the page that has been cached
6. verify that new entity and meta cache entries were created
7. reload the page and get prompted to save untyped data
(i'm guessing that step 5 could be replaced by waiting five minutes
for the cache to expire)
i've only been able to reproduce this in firefox (versions 1.0.7,
1.5.0.7, 2.0.0.20, 3.0.12 and 3.5.6) which seems to be the only
browser (and i tested in about 15 different versions of various
browsers) that gets a 304 response when clicking the reload button.
has anyone else experienced similar behavior or have any advice on
what i'm doing wrong in my configuration? the relavent bits are:
environment.rb
config.middleware.use ::Radiant::Cache, :use_x_accel_redirect = '/entity'
nginx.conf
location /entity {
internal;
root /radiant/tmp/cache;
}
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
