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 ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere For more information and to find out how you can switch, visit www.connectingforhealth.nhs.uk/nhsmail ******************************************************************************************************************** _______________________________________________ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
