[TYPO3-Performance] Where to put the "meat"?

[Dan Osipov]

Writing static files makes sense, however, we are moving towards more 
personalized content, that is constantly updating, so this is against 
what we're doing... We are planning to rely on Typo3 caching as well as 
PHP accelerators.

Our servers are fairly good, with several Quad core processors and up to 
16 Gb of RAM. We just need to decide if we want to put them towards 
handling MySQL tasks or PHP?

Dan Osipov
Calkins Media
http://danosipov.com/blog/

Olivier Dobberkau wrote:
> Dan Osipov schrieb:
> 
>> Thoughts?
> 
> my suggestion:
> 
> try to avoid typo3 for the frontend stuff as much as possible... :-)
> 
> use nginx to deliver static file, like statified html, jpg, pdf, etc
> instead of apache with php using your memory on the app servers.
> 
> -> nginx (proxy) -> apache -> php -> typo3
> 
> use a much caching as possible.
> 
> loadbalance the stuff. get as much memory per server as possible.
> 
> take a look at mysql proxy and use a master slave setup.
> 
> hope this gives you some thoughs..
> 
> olivier