[TYPO3-performance] TYPO3 4.4.4 Backend/JavaScript Performance on IE7/8 on newer PCs behind Firewall Contentfilter

Timo Bienk timo.bienk at apoexpress.de
Tue Nov 16 10:39:19 CET 2010


Hi there,

as mentioned above (Thread "TYPO3 4.4 Backend/JavaScript Performance on 
IE7/8 on older PCs") we are running into similar Problems.

Editor stop using BE because of the poor Performance since upgrading 
from 4.3 to 4.4. RTE feels very goopy: Contextual Menu e.g. will not 
show immediatly like before unter 4.3. And yes, Editor have high 
expectations... nevertheless a solution must be found.

Browser: IE7, now upgraded to IE8 with slightly improvement of 
performance but still not usable in the meaning of the editor.

Hardware: nearly-actual Dell PC, testing the BE with same user from a 
new Office-PC (Dualcore, >=1GB Ram). No perceptible enhancement. I won't 
blame the PCs.

OS: XP SP3

Server Connection: 100Mbit, Company Connection: 136Mbit
Not really a performance issue

WebServer env: Apache/2.2.15 (Unix) PHP/5.3.2 TYPO3 4.4.4
Cache-Control: no-cache, must-revalidate
Pragma: no-cache
Content-Encoding: gzip
Vary: Accept-Encoding
MS-Author-Via: DAV
Keep-Alive: timeout=15, max=499
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html;charset=utf-8

Firewall/AV/IDS: thats the snag, but this is the part in the puzzle we 
got absolutely no chance to configure to.
Talking to the sysadmins, we have deactivated BE compression by way of 
trial because of the (underpowered?) Firewallsystem/Proxy have to unpack 
gzipped js, css, html and check it for possible malware and compress all 
the files again after that and send it to the client. Deactivating BE 
compression gives us a slightly better performance, but still not enough 
says Editor. Even there is a poor CPU-Perfomance beside the Firewalls - 
4.3 went fine with this constellation.

Due to Company Policy there is no chance to use another browser than IE7 
or 8 even more not to bypass Security Phalanx.
The Solution found in the other Thread to step back to 4.3 is not really 
a Solution - maybe waiting to 4.5?

Is there something to fiddel about inside TYPO3 4.4 BE?
TIA
Regards, Timo


More information about the TYPO3-performance mailing list