TYPO3 Mailingliste: nicht fragen - lesen!

For a simple site of a few pages (but which may have heavy traffic, and some
database intensive extensions), which gives the best performance,
Templavoila or Modern Template Building/autoparser?


--
Simon Child


_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

On Sat, 23 Aug 2008 11:51:41 +0200, Simon Child <simon (AT) srchild (DOT) com> wrote:

> For a simple site of a few pages (but which may have heavy traffic, and
> some
> database intensive extensions), which gives the best performance,
> Templavoila or Modern Template Building/autoparser?
>
>

Hi Simon, i Whould guess it dosnet make much of a difference,
bacause renderd pages are normaly stored in cache in both systems. and
and for USER_INT extensions are marker inserted in these cache data.
these markers are then replace with the output of the USER_INT object.
all other objects / plugins are cached.

of course the will bee differences if you have a lot of no cachable pages.
or short cache interval's.

i don't know if anybody has made rendering-speed tests with
TemplaVoila vs Classic Template

i whould guess that classic template (without auto parser)
is faster templaViola. because there is just some search & replace
going on.

greets chris

--
Christian Wolff // Berlin
http://www.connye.com

Latest Projects:
http://www.bizim-tur.de/ | http://www.flycall.de | http://www.atr24.de
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

Simon Child wrote:
> For a simple site of a few pages (but which may have heavy traffic, and some
> database intensive extensions), which gives the best performance,
> Templavoila or Modern Template Building/autoparser?

Both are approximately the same. TV pre-parses template while MTB parses it each time. But TV does more other processing. But both TV and MTB take much less time than the rest of Frontend processing. So if you are trying to optimize speed, you need to look to something else, not TV or MTB.

--
Dmitry Dulepov
TYPO3 Core team
My TYPO3 book: http://www.packtpub.com/typo3-extens...velopment/book
In the blog: http://typo3bloke.net/pages/book-rev...garr-reynolds/
_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila

"Dmitry Dulepov [typo3]" <dmitry (AT) typo3 (DOT) org> wrote in message
news:mailman.1.1219656709.13061.typo3-project-templavoila (AT) lists (DOT) netfielders.de...

> Both are approximately the same. TV pre-parses template while MTB parses
> it each time. But TV does more other processing. But both TV and MTB take
> much less time than the rest of Frontend processing. So if you are trying
> to optimize speed, you need to look to something else, not TV or MTB.

Thanks, I've gone with TV (I realised that had forgotten how to use
autoparser! and guessed there wouldn't be much difference anyway)

--
Simon Child


_______________________________________________
TYPO3-project-templavoila mailing list
TYPO3-project-templavoila (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-templavoila