Quote from: oori at Aug 03, 2010, 09:04 PMThe context-cache is really the only bottleneck at this point, and this will be solved very soon using some new storage techniques for representing hierarchies. You can turn the context cache off, but at the moment, the makeUrl() functionality has to basically build the entire context cache in memory to use it on each page load where a link appears and is not cacheable.
in a blog with ten-thousand resources, context cache will get quite big, what else? (front-end performance only, /manager is not important)
Have you any revo installation with huge amount of resources? can you point us to the bottle-necks.
side-note: as far as i see in today’s web apps - caching is the main key to performance (in terms of page load time).
MODX Staff
Yes, these changes have been pushed to 2.1 release because they have some side-effects that warrant not going into a bug-fix release. But they are already under development.
Quote from: OpenGeek at Aug 04, 2010, 11:57 AM
The context-cache is really the only bottleneck at this point, and this will be solved very soon using some new storage techniques for representing hierarchies. You can turn the context cache off, but at the moment, the makeUrl() functionality has to basically build the entire context cache in memory to use it on each page load where a link appears and is not cacheable.
Is there any news about new storage techniques?