[TYPO3] TYPO3 performance; Is it too slow for high-traffic sites?

[Guillermo Prandi]

Steffen Müller wrote:
> Hi.
>
> On 03.11.2006 02:07 Guillermo Prandi wrote:
>   
>> Hi. I wish to hear your thoughts about how well does TYPO3 perform on
>> high-traffic sites. For instance, I wish to implement a complex site
>> including multilanguage weblogs and other dynamic data, and I expect
>> thousands of hits per hour (mostly reads). What is your experience on
>> this kind of load? The database will be a well-tuned Oracle 9.2 server.
>>     
>
> It depends on what kind of extensions (weblog) you use. Any frontend
> extension, which does not support caching, will be a performance killer.
> (including 100% personalized pages with logged in FE-users)
>
> I have never used TYPO3 as a weblog, so I cannot provide specific
> information about that.
>
> "thousands of hits per hour" does not mean much traffic (3600 hits/h =
> average of 1 hit/s) - except if 90% of thoses thousands comes within one
> minute. But even if you get slashdotted, there might be a solution to
> stay online, e.g. by using reverse-proxy, enabling you to serve >1000
> pages/second (!)
>
> So my answer is yes.
>
> There's a chapter about performance in the wiki
> http://wiki.typo3.org/index.php/Performance_tuning
>
> Please regret the self-advertising hint to
> http://typo3.org/development/articles/testing-and-tuning-typo3-performance/
>
> Last but not least, Michael had a great performance on performance:
> http://castor.t3o.punkt.de/files/podkast_7minutes-performance.m4v
>   
Juergen Egeling wrote:
> What kind of load? You are not writing anything about the load, except
> "Thousands per hour", which could be anything from 1500 to 500000 per hour.
> IMHO th einteresting number is the peak per second.
> Also "Mostly" read. What ratio? 90% read? or 55%?
>
>   
>> The database will be a well-tuned Oracle 9.2 server.
>>     
> I read this somewhere else as well. The bottleneck than was the LAN ;-))
>
> Anyway: I am pretty sure, it will work with TYPO3, but you have to give
> some thoughts to the setup, who writes when where, how to cache, what
> to cache, reverse proxies, etc. pp.
> I am also pretty sure, that i *won't* work with TYPO3, if one sets it up 
> wrong.
>
> best
> Juergen
>   
Dmitry Dulepov wrote:
> Hi!
>   
> Very good experience, though I do not think you need oracle there.
>
> It is always a question of optimization. If you know how to do it, of 
> course ;)
>   
Thank you, guys for your answers. I'm sorry about being vague about the 
actual server load, but for the moment any figures are mere speculation. 
I only know that the site must scale well in the end.

Peak load will not fall below 15 pages/second, I imagine.

By mostly read I meant 1 of every 10 accesses will modify the database 
and invalidate some (or many) cached pages. Unfortunately, the number of 
users will be in the thousands (1,000? 10,000? I don't know!) and each 
user will get a particular view of the site (personalized content), 
although part of it could be cacheable (e.g., sidebar contents). I will 
be bothering you guys about caching strategies when I had learned some 
TYPO3 basics at least. :)

The fact that the project will use Oracle is not for performance, but 
because it will be integrated with an existing site and database. I was 
just mentioning it for completeness.

The clumsy tests I made with my old PC (Athlon XP 1600, 1GB RAM) with 
Apache, PHP 4.4, MySQL 4 (InnoDB tables) and TYPO3 3.8 (QuickStart 
example) were frustratingly slow for single-page requests, so I started 
to worry. I'm doing some more tests and some of the slowness seem to 
have disappeared (at least from the FE, although BE pages still take >1 
sec. to render). I am aware that my PC is slow and single-processor (CPU 
time taken by the user agent is stolen from the web server's), but it 
still seemed pretty slow to me. I look forward to further experimenting 
with TYPO3 to get more useful results.

Take care,

Guille