[TYPO3-english] Typo3 4.5.3 intranet relaunch, what else should I consider?

[Olivier Dobberkau]

Am 20.12.11 13:08, schrieb Floy Mark (LEWISHAM HEALTHCARE NHS TRUST):

> Hello,
> 
> A few weeks ago our first attempt at an Intranet go-live worked fine up until just past lunchtime when Typo3 became unresponsive. Since then we have seriously beefed up resources on both DB and Web servers to handle possible load spikes. Apache Benchmarking results gives us confidence in our builds as we head towards another go-live.
> 
> My question now is what else should we be considering before our next go-live attempt? Unfortunately I had removed Web and DB server logging and have not been able to duplicate the scenario, so I am assuming the original issue was in or around request traffic volumes.
> 
> When Typo3 crashed it reported that it could not connect to the database. Then suddenly, without making any changes, the database became available and Typo3 sprang back into action the very next day.
> 
> 
> Many thanks for any help,
> Mark

Hey Mark,

my glasbulb is broken right now. :-)

you might want to hire some experts to analyse your setup.

my experiences tell me:

* bad or no caching settings on all app layers
* bloated apache settings
* mysql and apache on the same host eating up their memory

best regards,

olivier