> Right. Caching the complete url in the database would help, > but would > not work in all cases, i.e. virtual pages that represent > multiple urls. > Perhaps we should try this and get some metrics?
I was thinking that there would be a Page#calculate_urls method that would by default just return the result of Page#url but could be overridden to return multiple urls (in the case where a page knows all its urls) - otherwise there's the fallback to doing the tree search. I just did one quick metric - on my system, with ~900 pages, doing an update of the url cache for all pages 50 times took ~19 seconds - that's ~.4ms per page. Scaling up, that's 4 seconds if you modify a page with 10,000 children... I think that would be a reasonable response time... so the disadvantage at that end seems reasonable - just need to find out if the advantages are worth it. Dan. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
