[TYPO3-performance] Scaling TYPO3 horizontally

Nico Pieters nico at tidi.be
Tue Jul 23 09:18:27 CEST 2013


Good morning,

We are experimenting with Newrelic as a diagnostic tool. It breaks down the
application based on live information. It will help you to so what exactly
is slow.

With kind regards,

Nico


2013/7/23 Philipp <philippwrann at gmx.at>

> We use APC and memcached (i think mostly because of comfort). For Frontend
> accelleration we use google page speed. Standard Apache/PHP config (PHP
> 5.3).
>
> Caches are fast enough now but uncached actions and first-page-requests
> are killers.
>
> Id like to hear something about the boosting of those first-requests, what
> are the worst performance killers you experienced? Our Frontpage is pretty
> massive, carrying many plugins, uncompressed HTML output ~ 1.5Megs. Cached
> this page serves in about 300ms, thats fast enough for us.
>
> But uncached it can increase to 2-3 seconds, when compiling less +1.5
> seconds.
>
> From which improvements would we have the greatest benefits you think?
> SQL? (We use MySQL)
> Typoscript? Our final template has about 7700 lines
> Views? Change to Standalone PHP Views instead of Fluid Views?
>
> I would like to decrease the parseingtime of a uncached page-request to <
> 1000ms and a dynamic pluginRequest to < 400ms.
>
> kind regards
>
> ______________________________**_________________
> TYPO3-performance mailing list
> TYPO3-performance at lists.typo3.**org <TYPO3-performance at lists.typo3.org>
> http://lists.typo3.org/cgi-**bin/mailman/listinfo/typo3-**performance<http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-performance>
>



-- 
Nico Pieters
Tidi Solutions

nico at tidi.be
+32 495 303 594

www.tidi.be
www.netwerklounge.be


More information about the TYPO3-performance mailing list