Performance issue building section structure

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

qsdmv

It seems that there is a big performance issue for the current architect when you have over thousands of sections. I have around 3,000 section. The current structure is actually building whole section structure then cache it. Can we change by using smart incremental way so that we build the partial section structure when we really need. If front user never accesses some of sections, why do we need to build it and cache it? For example, we can build 33% section structure (most often accessed), then another 33% if we need to access them, then final 33% if we need to access.

qsdmv

Brian Remmington, do you have any comment or suggestion?

For example, if user accesses /section1/section2/section3/section/4, we only need to cache all of those sections. If user accesses /section21/section/22/section/23/section/24, then those sections are cached. Whole section tree structure building process is really expensive, cost and inefficient. If we can re-work this, it would be perfect.