Bug #19655
closed
Extreme performance decrease
0%
Description
Hello,
i just tested the new 4.3.0alpha1 release (svn trunk from yesterday (11/27/2008) 20:00) and have extreme performance problems.
If a page isn't cached, my system needs 4 times longer to cache the page and create an output. Even is a page is cached, the output takes quite longer then before. fe_edit and simulatestatic are deactivated. The install tool has also be checked the db x-times. All tables are perfect. The new caching system should work.
I've also installed memcached and started it normally with my system.
Is there any suggestion which could be wrong?
The system previously runs under TYPO3 4.2.3 without any issues.
(issue imported from #M9854)
Updated by Christian Kuhn almost 16 years ago
Could you proove this by adding some numbers? For me 4.2.3 is (roughly) as fast as trunk.
You could set $TYPO3_CONF_VARS['FE']['debug'] = '1'; in localconf.php. This will add the total parsetime of the page in a comment at the bottom of your FE html output.
Updated by Dmitry Dulepov almost 16 years ago
Firsts, just installing memcached will not help, TYPO3 must be configured to use it.
Secondly, memcached support in TYPO3 was broken until December 1st (see #19506).
Thirdly, please, check again your database in the database analyzer.
Updated by Daniel Felix almost 16 years ago
I get the last trunk with the fixed memcached-support and two other bugfixes which broke down the performance.
The system now properly use the memcached-support and the loops are also done (some pages where generated 2 times because the first generation failes and gives a blank page).
The database is also correct.
I have no more errors in my syslog since the fixes.
My loading times are 1/5 faster in relation to TYPO3 4.2.3.
The loading times with the previous svn-trunk where beyond good and evil (sometimes 20 or 30 seconds for just a simple page).
This ticket can be closed.
Updated by Daniel Felix almost 16 years ago
By the way...
memcached should automatically work for TYPO3 in the current trunk, or?
Or is there any checkbox in the install tool which needs a "click"?
Updated by Marcus Krause almost 16 years ago
Setting to resolved as reporter claims it's fixed in the meantime in trunk.