It starts already during logon to backend:
http://localhost/typo3_13_4_0ip/typo3/ajax/login/preflight with this response: {"capabilities":{"cookie":true,"referrer":true}} takes 8 seconds

getting cache tokens like: http://localhost/typo3_13_4_0ip/typo3/ajax/icons/cache?token=b2599c41e43cf522fb05a3a3b51307333ab6d32a with minimal response takes 9 Seconds.

Getting layout token to open in introduction package a sample page http://localhost/typo3_13_4_0ip/typo3/module/web/layout?token=546ef8722d70c7dc3e3a48b11c66a3d2b66a06df&id=79 takes 12 seconds

cpu and memory is low round about 10% , machine is a p1 with enough resources. All cache settings like suggestions:

php settings

memory_limit = 2048M
post_max_size = 40M
upload_max_filesize = 40M

Optimize MySQL settings:

innodb_buffer_pool_size = 512M
innodb_log_file_size = 128M
max_allowed_packet = 128M

changing from localhost to 127.0.0.1 does not make a difference. Is there any possibilty to spped this up. XDebug is even off.

It starts already during logon to backend:
http://localhost/typo3_13_4_0ip/typo3/ajax/login/preflight with this response: {"capabilities":{"cookie":true,"referrer":true}} takes 8 seconds

getting cache tokens like: http://localhost/typo3_13_4_0ip/typo3/ajax/icons/cache?token=b2599c41e43cf522fb05a3a3b51307333ab6d32a with minimal response takes 9 Seconds.

Getting layout token to open in introduction package a sample page http://localhost/typo3_13_4_0ip/typo3/module/web/layout?token=546ef8722d70c7dc3e3a48b11c66a3d2b66a06df&id=79 takes 12 seconds

cpu and memory is low round about 10% , machine is a p1 with enough resources. All cache settings like suggestions:

php settings

memory_limit = 2048M
post_max_size = 40M
upload_max_filesize = 40M

Optimize MySQL settings:

innodb_buffer_pool_size = 512M
innodb_log_file_size = 128M
max_allowed_packet = 128M

changing from localhost to 127.0.0.1 does not make a difference. Is there any possibilty to spped this up. XDebug is even off.

• xampp
• typo3

Share Improve this question Follow asked Nov 20, 2024 at 17:51 eckardeckard 1133 bronze badges 2

• is it also so slow if you set memory_limit to 256M or 512M only? – David Commented Nov 21, 2024 at 11:05
• actually it does not make any difference. It is not faster with less memory limit – eckard Commented Nov 28, 2024 at 13:52

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

The described behaviour often boils down to the usage of xdebug, enabled by default even with no client (IDE) listening to it.

XDebug is even off

Please recheck this, at best completly remove xdebug to be sure.

Further, check if you have any other profiling things installed and active, for example xhprof, blackfire, tidyways or other APM/profile.

The stated timings are really off, special for backend standard views.

Otherwise, this would mean a really really really bad and slow harddisk. Not sure about your complete setup, do you have your project (docroot) on some kind of external usb drive or network storage (mountend) ?

Another point could be, that you have disabled all caches by reconfigure it to the NullBackend - or at least some essential ones.

You could also try to switch to pdo_mysql if you are using mysqli as database driver, or the way around if that helps.

Don't know the insight how xampp/wampp is build nowerdays and the internal webserver/setup/php integration. In general, it could also be some timeouts, stacking, poolings depending on webserver and configuration.

Otherwise - you need to get some profile and profile which takes the time, at least casual TYPO3 installation should not have such timings - even with really lot of data and pages.

You could try to do the cache:warmup on TYPO3 v12 before trying to load it in the web:

vendor/bin/typo3 cache:warmup

for a composer installation (casual setup) - or

typo3/sysext/core/bin/typo3 cache:warmup