Performance problem with live serach and be_acl
|Priority:||Must have||Due date:|
Especially we did the following fixes:
- reduce overhead: we check before we render the pagetree if page-id is already in the pagelist: this is pretty handy for admins
- we added a hook to the function getAvailablePageIds: e.g. be_acl holds all the information about pages that a BE-User has right to access. There is no need to calculate ist again and again.
Updated by Oliver Hader about 1 year ago
Could you please push your patch to review.typo3.org, so that other's can test and review your contribution?
Get further information on how to do this here: http://wiki.typo3.org/Contribution_Walkthrough_Tutorials
Besides that, your patch changes some API calls (e.g. from comma-separate-list to array), thus a check whether an array/string is given seems to be required for backwards compatibility...
Updated by Georg Ringer about 1 year ago
be aware that be_acl itself has great problems with performance if you got many acl records in your system.
Updated by Peter Russ about 1 year ago
@Georg: we aware of that. be_acl is completely refactored using caching framework. that the reason why we request the patch in t3lib_search_livesearch.