-
Bug
-
Resolution: Fixed
-
Medium
-
2.7
-
None
Internal view of CONF-10333, from CSP-1435.
In the support issue, the user had ~6000 pages in a space. Current logic has three "slow" points:
1. When the user clicks "Alphabetical", the search is run on the whole space.
2. In listpages-alphaview.vm the getItems call (which runs the search) is directly called twice in addition to the (correct) call through the paginationSupport delegate.
3. The search itself "getPermittedEntitiesOf(spaceManager.getPagesStartingWith(getSpace(), startString));" is very slow.
1 is a design problem - no upper limit is set on the number of pages returned
2 is an easy fix, doing now.
3 is the actual problem - Charles' comments in CONf-9972 could be very helpful.
- blocks
-
CONFSERVER-4710 Rendering spaces containing 1000+ pages slow
- Closed
-
CONFSERVER-9972 Accessing list of alphabetical index for pages in a space causes NPE transaction
- Closed
- causes
-
CONFSERVER-14072 Alphabetical listing of pages does not work when there are too many pages beginning with a letter
- Closed
- is related to
-
CONFSERVER-13373 Tree View hangs Internet Explorer when viewing lots of pages at once
- Closed
-
CONFSERVER-9972 Accessing list of alphabetical index for pages in a space causes NPE transaction
- Closed
-
CONFSERVER-10333 alphabetical & tree view for pages just hangs when clicked in browse space
- Closed
-
CONFSERVER-13611 Improve performance by using read-only view/result transaction in XWork transaction interceptor
- Closed
- relates to
-
CONFSERVER-11860 Pagetree component causing errors in large spaces
- Closed
-
CONFSERVER-4710 Rendering spaces containing 1000+ pages slow
- Closed
-
CONFSERVER-9972 Accessing list of alphabetical index for pages in a space causes NPE transaction
- Closed
-
CONFSERVER-12489 Allow Text Entry in Addition to Tree Viewer when moving a page to a new parent
- Closed