[TYPO3-Performance] General questions

Mathias Schreiber [TYPO3] mathias at typo3.org
Mon Aug 4 10:36:28 CEST 2008


Dmitry Dulepov [typo3] schrieb:
> Hi!
> 
> Mathias Schreiber [TYPO3] wrote:
>> So we reduce the data being transfered from the DB server to the 
>> apache server.
>> I don't see the big "breakthrough" in TYPO3 performance.
> 
> You don't but many MySQL professionals do. They say such compression 
> improve application performance a lot. And they even provide numbers. 
> Are you good enough in MySQL to say it will not improve performance?

I'll try it with numbers then:
Does compressing 10.000 mysql queries make TYPO3 faster than just 
sending 120 queries?

You see, the problem is that TYPO3 does too may queries which are not 
needed.

> It looks like you do not really want to do anything.

I suggest we stick to facts - I know that TYPO3 does things three times 
which are needed once.
I know that someone build in caching into functions that are called over 
and over (which is a good thing) but kills the cache each time the 
function is called (which is rather.... unsmart).

> You argue but you do not try what other people propose to you.

Serious performance tuning is a matter of analysis.
"Trying" has nothing to do with analysis.

 > What's the point to discuss it then?

The point is that we have problems in several "severities".
MySQL itself isn't too slow.
So why does TYPO3 become slow?

Might be many factors, one definetly is that is sends too many queries.
This is something we need to work on.
Other factors will have to be isolated, this is where the workload of 
tuning is.

So my point is to work on stuff we KNOW, not what we "think it might be".

And after we did the basics querying MySQL, we can start thinking about 
improving MySQL performance itself.
And after that we can think about caching mechanisms in TYPO3.
And then static file caching.

I think it is dangerous to claim that uncached content isn't a problem 
if it takes ages to render, because everything is good once it is cached.

My intention is to get rid of stuff that is happening before a page is 
being cached.
Once we are fast enough there we can work on caching.

best Mattes

P.S. If you all want to have some fun, set up a website with TYPO3 3.5.
I did for fun and it does exactely the same thing as 4.2.0 but is three 
times faster :)

P.P.S. less personal attacks would be highly appreciated


-- 
T3A AM
Rocking TYPO3 since 3.1b1


More information about the TYPO3-Performance mailing list