[TYPO3-v4] Core performance for 4.6 and beyond

[Steffen Kamper]

Hi Dmitry,

Am 10.02.2011 20:54, schrieb Dmitry Dulepov:
> Hi!
>
> Steffen Kamper wrote:
>> So what is best? Instead of controverse discussion we could try to solve
>> bottlenecks with first
>> * find the bottlenecks!
>
> They are known for ages. Top issues:

some yes, but very rare devs try to work on them. From time to time some 
of these were optimized, but not enough.

> - multiple requests for the same record in the core, especially fetching
> the same record with various fields but the same where condition
> (pollutes the cache, does not use cache well)

now it's easy to log queries. I already did, and this WE i will continue 
doing this together with Rupi.

> - rootline fetching

yes :)

> - suboptimal user group handling

it seems that there will be a taskforce for (fe) - i think you meant 
fe_groups.

> - speaking URL processing in Frontend

agree

> - bad database indexes

please make suggestions.

>
> Those are major problems for sites with many pages and a lot of
> visitors. If TYPO3 wants to fix them, it needs certain major changes, like:
> - making centralized access to records inside TYPO3 core: no direct
> database access but a record storage, which will cache records at least
> in memory for the current request
> - modify hierarchical structures to fetch data using a single request
> - optimize FE user session fetching, that does more work than necessary
> - move RealURL processing to the core, making it integral part, which
> does most of its logic inside the Backend, not Frontend
> - review USER/USER_INT model to provide better handling for form
> submission out of the box (now there is no good way to do it in TYPO3)
> - allow caching on per-user basis, this would reduce number of USER_INT
> objects
> - implement out of the box cache for template files
>

very good points. Are you willing to help to get some things done? I 
totally agree with realurl in core. Everyone needs it, and it could be 
calculated in BE much easier, and there we need you and your experience


> I can continue but this is enough for start.
>

please continue. It's good to have such list. I would like to gather all 
and bring them to a wiki page. This is a good point to find an issue to 
work on. 4.6 gives a good chance to kill some old habits just for 
compatibility but making a real and stable and performant API.

vg Steffen