#88474Page tree performance in 9.5
Description
The new page tree delivered in v.9.5 has performance issues with bigger instalations e.g. 100k pages
Because of processing the whole page tree in one go.
We should make it possible to fetch one page tree level at once and process only these pages on PHP side.
For the discussion please join the slack channel
#page-tree-performance
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Subtasks 7
- Bug #86945Performance PageTree in Workspace
- Bug #88097Page tree data fetching is using a huge amount of memory in PHP
- Bug #88098Page tree XHR is fetching huge JSON data
- Bug #88943Pagetree taking extremely long to load for editors
- Bug #89687Page tree sends unnecessary data
- Bug #91036Do not calculate beuser page permissions for every page
- Task #91037Tune permission check in page tree
Related issues 11
- Bug #90056Selection not open after after leaving filtered mode
- Task #90104Introduce prepared statement for BackendUtility::getPageForRootline
- Task #90105Allow full row to be passed into isInWebMount()
- Bug #91728Very slow tree loading if you have multiple workspaces TYPO3 v10
- Bug #91883Filtering in the page tree shows translated pages alongside the L=0 ones
- Bug #91884Page tree filter has no delete "X", needs hitting enter and has no filter info box anymore, a big backwards step regarding usability
- Bug #91885Page-Tree filter does not reset
- Bug #91887Page-Tree filter does not indicate its state
- Bug #91902Page tree not expanding deeper from initial view for editors
- Bug #92027Reset page tree filter after deletion of page record
- Epic #93547Collection of problems with large sites