[TYPO3-dev] [TYPO3-performance] Scaling TYPO3 horizontally

[Christian Ludwig]

Hi Stefan,

Due to the small amount of hits on these pages there was no need in
caching the dynamic pages. We are using a patched version of moc_varnish
(or is there an other extension for TYPO3?) and tried out the "ESI
Features", but unfortunately they did not work out of the box. Because
of the lack of budget and time and enough performance, we could not digg
further into ESI.

We prefered using NginX as a https proxy only (without caching) because
we wanted all caching to be managed and configured in one central
application. In addition Varnish holds its cache in memory what is much
faster than fetching static files from disk.

Greetings
Christian

-----Original Message-----
From: typo3-dev-bounces at lists.typo3.org
[mailto:typo3-dev-bounces at lists.typo3.org] On Behalf Of Stefan Neufeind
Sent: Friday, September 13, 2013 5:32 PM
To: List for Core-/Extension development
Subject: Re: [TYPO3-dev] [TYPO3-performance] Scaling TYPO3 horizontally

Hi,

but then why don't you use nginx directly for the caching of images
etc., or even with it's integrated webserver to also fetch the static
files from disk.

Furthermore, if you pass dynamic requests straight through, you don't
take advantage of caching pages as well. That would be possible with
"aggressive" caching in Varnish and then using something like the
varnish-TYPO3-module to actively inform varnish which pages were purged
from the cache/became invalid.


Kind regards,
 Stefan