Closed peakpg closed 12 years ago
Thats true. I will also try to look at this issue.
This is completed and released in v3.1.5. The sitemap has major performance improvements, and pages and the content library are faster as well. It will be ported forward into v3.3.3 as well.
On larger sites (with many many pages/sections/files) performance can become an issue. Initial research has tied this back to how pages and sections are structured, which results in a large number of queries to build menu navigation. This affects both the sitemap as well as individual pages which use menu tags.
This will need some more research, but the initial goal will likely be to reduce the number of calls to construct the tree (possibly through the use of a gem like Ancestry https://github.com/stefankroes/ancestry ) . In addition, I will look at moving all path related lookups to a single table, to avoid having to do multiple SQL calls just to determine if there is a 404 missing resource.