> > Andrew: You may want to avoid deep directory hierarchies on > your site > > due to the recursive database queries Radiant performs. > > > > Oliver > > Oh, good point. How deep is "deep"? Does radiant execute a query for > each level of the page tree that it traverses (and on each request)? > Could some kind of caching solution like memcached (or even just > storing it in memory) be used instead (or is it already)?
This is no longer a problem - Radiant will currently run one database query for each level of the page heirachy, but it's only one query, which isn't going to add up to anything significant for any reasonable value of 'deep' on a website. Cached pages don't hit the database at all and get served much faster than via rail's regular caching mechanism - It's 5-10 times slower than serving a raw html page through apache, but you'll probably find that that's more than fast enough. Radiant previously had a problem with WIDE directory heirachies - every sibling would be loaded on the way down the tree - but that is no longer the case for pages the use the regular slug mechanism (ie, child url is /parent-url/slug) - Pages such as the ArchivePage that rewrite the child urls (to, ie. /parent-url/year/month/day/slug) will still exhibit that behaviour, but it's a fairly simple problem to fix - I just have to get around to running benchmarks on it, which is a bit of a PITA. Back to the original question, I think I'm probably running the largest radiant site (http://www.thegroggysquirrel.com) - upwards of 1100 pages - most of these pages are in very wide heirachies (95% of my pages are direct children of either /comics or /articles) and have parent pages that rewrite their urls - pretty much the worst case scenario for radiant performance, but my site performs fine. Dan. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
