[TYPO3-performance] 4.7 to 6.2 slow down

[Andi]

use nc_static_filecache
optimize your .htaccess
enable compression
merge scripts

optimize your images
reduce requests

forget about facebook or google they are very slow! use scripts which do not connect at pageload. 

use lazy image loading

if you can't reach a yslow value higher than 95 than you have still something wrong so read the report what it is

afterwards read the pagespeed report and optimize to get a value higher than 95

still not good than outsource all scripts and images to a second domain and call them from there to enable parallel loading

finally connect your site to cloudflare. com and your gtmwtrix value will go up to 97/98 and higher

still not satisfied pack your side on digital ocean for start 5$ and sie the difference. 

if the side still won't work like you want than change simply the system and migrate your site with the migrator to processwire - this is really fast!

Andi
(Andreas Becker)

15/21 M.2 Viset Road
Rawai, Muang, Phuket
83130 Thailand

+66 (0)81 606 3378
+66 (0)76 38 33 08
+49 (0)711 50 88788 50 -2
+49 (0)711 50 88788 59 Fax

Skype: lisandi
GoogleTalk: andi at lisandi.com
GoogleTalk: cocopapa
Youtube: apapococ
Facebook: andibecker
Flickr: andibecker


> On Sep 22, 2014, at 13:53, Philipp Wrann <philippwrann at gmail.com> wrote:
> 
> Of course using the ORM is slower than plain SQL
> 
> ORMs do mapping, the map all results in objects, if objects have other entities as properties that are not lazy additional queries are made
> ORMs do select * and therfore cant do indexonly queries
> 
> But why do you need to load 1000 Entities at once?
> When setting up the model proper and doing regular stuff (eg load 10-20 entities and implement some kind of paging) TYPO3 6.2 is quiet fast.
> 
> Important:
> Add @lazy to all properties that are not simple (1:1, 1:N, M:N Relations) Set up APC Caching for all possible caches
> Dont render the same link multiple times, use alias viewhelper to assign a generated URI and use it multiple times
> Dont render many different image sizes, try to only use 2-3 variants
> Avoid uncached elements, this is where TYPO3 6x compared to TYPO3 4x sucks.
> _______________________________________________
> TYPO3-performance mailing list
> TYPO3-performance at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-performance