On Mon, Mar 22, 2010 at 14:33, qutic development <mailinglists@qutic.com> wrote:
We were digging deep into radiant and found that only a small change in the 'parse_object' method is speeding up radiant a lot! Especially if you use the shared_layout extension and inline radius tags.
Hello,
I'm interested in improving Radiant performance because I've recently deployed it for a non-profit which has a slower web server and it doesn't performing satisfactory (both page rendering and admin interface).
The bottlenecks are Radius and Shards in the admin interface.
This is why I started porting Radiant to rails3 and playing around with some optimizations locally.
I'm looking forward to your optimizations, but my suggestion is to fork radiant and actually commit your changes so that we can see them, try it out and, if it doesn't break tests, pull that in.
You should also test if the test coverage is satisfactory for areas which you are changing. If not, add more tests in commits prior to optimization ones. Thanks
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/
To unsubscribe from this group, send email to radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
No comments:
Post a Comment