[TYPO3-v4] Core performance for 4.6 and beyond

Dmitry Dulepov dmitry.dulepov at gmail.com
Thu Feb 10 20:54:59 CET 2011


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:
- 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)
- rootline fetching
- suboptimal user group handling
- speaking URL processing in Frontend
- bad database indexes

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

I can continue but this is enough for start.

-- 
Dmitry Dulepov
TYPO3 core&security team member
E-mail: dmitry.dulepov at typo3.org
Web: http://dmitry-dulepov.com/


More information about the TYPO3-project-v4 mailing list