[TYPO3-Performance] General questions

[Mathias Schreiber [TYPO3]]

Martin Kutschker schrieb:
> Mathias Schreiber [TYPO3] schrieb:
>> Dmitry Dulepov [typo3] schrieb:
>>> Hi!
>>>
>>> Mathias Schreiber [TYPO3] wrote:
>>>> Seperating DB and Apache made one thing quite easy to see...
>>>> Within a week the DB server and Apaches have exchanged 220GB of data
>>>> - which is three times the effective traffic of webpages being
>>>> delivered.
>>> There was a patch from me in the core list to enable compressing for
>>> such cases. It will save you huge amount of traffic and give a good
>>> boost of performance. This is the first thing to do.
>> how exactely does your patch compress mysql related database traffic?
>> I'm talking about "Hey MySQL Server, gimme the rootline for page ID 14"
>> or to be more precise... "MySQL, give me parent page of 14, ah, page ID
>> 3, now give me parent page of 3".
> 
> How do you use the word "compress"? Do you mean "reducing" the run time
> of the queries?

No.
If you followed the thread you see that I don't bitch about internal 
network traffic (basically I don't care about fiberchannel traffic), but 
the fact that TYPO3 talks to MySQL MUCH too much is something we need to 
change.

So by pointing out the 220GB network traffic MySQL <-> TYPO3 I wanted to 
show that there are too many queries, not too much pure traffic.

> Dmitry is talking about the compression of the data on
> the transfer. Mysql has an option to compress/decompress the data sent
> over the network on-the-fly (see docs). This will reduce the bandwith
> used for transferring the query results from the Mysql server to the client.

Ok.
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.

best
Mattes

-- 
T3A AM
Rocking TYPO3 since 3.1b1