[TYPO3-dev] Very bad BE performance when loading the form for creating/editing a CE

[Uschi Renziehausen]

Hello Oliver,

I thank you a lot for your answer and for your questions. For the 
questions, I will not be able to answer most of them before tuesday 
because I simply do not know how or do not have the rights to find out. 
But I will try hard, can you stay tuned, please :-)

Uschi



Oliver Rowlands wrote:
> Hi Uschi,
> 
> be_acl might be one of your problems as it adds a lot of complexity to 
> the backend permissions logic.
> 
> Though I doubt this is the root of your problems as your backend page 
> loading times sound rather slow.
> 
> When it comes to TYPO3 performance there are a number of issues which 
> you need to be consider:
> 
> - Server hardware specification: what type of hardware are you currently 
> running your project on?
> 
> - Filesystem optimisations: what filesystem are you currently using? Has 
> it been optimised?
> 
> - PHP pre-processor: are you running a PHP accelerator (eg: eAccelerator)?
> 
> - mySQL optimisation: has your mySQL configuration been optimised for 
> your hardware? Are you using query caching? Are you running your tables 
> in myISAM or InnoDB?
> 
> - TYPO3 backend optimisations: have you optimised the TYPO3 backend? 
> Michiel posted a good article about the issue on his blog last month [1].
> 
> We currently run a number of large TYPO3 sites (5000+ pages) and have 
> not had any major performance issues with the backend as long as 
> everything has been optimised correctly.
> 
> The only problem we have had in the past is with large numbers of 
> sibling pages in the same branch of the page tree. In this case using 
> the local 'Mount as treeroot' option usually solved the problem.
> 
> Best regards,
> 
> Oliver
> 
> [1] http://typofree.org/articles/optimizing-typo3-backend-responsiveness/
> 
> Uschi Renziehausen wrote:
>> Dear devs,
>>
>> in our university project we encountered a performance problem that 
>> makes certain parts of the BE very frustrating to use for ordinary 
>> authors when working with CE forms like text or text with image.
>>
>> Situation:
>> - Pagetree currently has 2500 pages and will at least double up in the 
>> following 3 months.
>> - ALL editors need to be able to link to ALL pages of the tree (e.g. 
>> using CType menu) regardless whether they are allowed to edit a page 
>> or not. That means, they need at read access to the whole pagetree.
>> - We are using be_acl, typo3 4.2 dev (latest branch).
>> - Each editors' group has at least 2 dbmounts
>>     a) one for the part of the pagetree they are responsible for
>>     b) one for the whole pagetree with read only to be able to link to 
>> all pages
>>
>>
>> Some statistics:
>> I made some tests by  simply counting how long it takes to load 
>> something.
>>
>> As an admin
>>
>> Loading the pagetree (Web->Page): 3
>> Loading pagecontent (clicking on the title of a page): 2
>> Loading CE Text form (clicking on the icon in new content element 
>> wizard): 3
>> Saving the CE Text: 3
>>
>> As an editor with only one DB-mount a (some 80 pages)
>>
>> Loading the pagetree (Web->Page): 3
>> Loading pagecontent (clicking on the title of a page): 3
>> Loading CE Text form (clicking on the icon in new content element 
>> wizard): 5 (!!!)
>> Saving the CE Text: 5
>>
>>
>> As an editor with 2 DB-mounts (a and b)
>>
>> Loading the pagetree (Web->Page): 5
>> Loading pagecontent (clicking on the title of a page): 4
>> Loading CE Text form (clicking on the icon in new content element 
>> wizard): 18 (!!!)
>> Saving the CE Text: 6
>>
>> As you can see, the size of the pagetree has an enormous impact on how 
>> long it takes to load the editing form for a CE. Counting to 18 until 
>> a form shows up will put editors into a very bad mood.
>>
>> Any ideas what might be the bottleneck and how performance could be 
>> improved?
>>
>> Regards, Uschi
> 
>