Project

General

Profile

Actions

Bug #48688

closed

FE Rendering of Typo3 4.5.27 slower than 4.5.25

Added by Webadmin no-lastname-given over 11 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Performance
Target version:
-
Start date:
2013-05-31
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

We just upgraded from 4.5.25 to 4.5.27. The backend (list module) is much faster now, but the frontend rendering slowed down. For example a page which takes around 500ms with 4.5.25 now needs more than 1.3 seconds.

It's reproducible when we switch from one version to the other one.

Plugins could not be the reason for this problems. We testet it with an empty page (only some HMENUS)


Files

upgrade.PNG (37.3 KB) upgrade.PNG Webadmin no-lastname-given, 2013-12-12 16:00
upgrade2.PNG (67.2 KB) upgrade2.PNG Webadmin no-lastname-given, 2013-12-12 16:00

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #34446: undefined variable imgExt in tslib_content.phpClosed2012-03-01

Actions
Actions #1

Updated by Thorsten Kahler over 11 years ago

  • Status changed from New to Needs Feedback

Could you please test with an even more simple TS configuration, e.g. only a single TEXT element or the like.

Some more information about your testing setup might help to verify your numbers, e.g.
  • dedicated test server?
  • possible network interferences?
  • how did you measure (tools)?
  • single server or dedicated servers for web/db?
  • ...
Actions #2

Updated by Webadmin no-lastname-given over 11 years ago

Sorry, here are the details:

  • Decidated live server (8Cores, 16GB RAM, Debian 6.0)
  • No network interferences (Decidated line)
  • We measured with the network tool of Chrome
  • Single Server for web and db, but the time spent in db is equal to the old version (checked with newrelic.com)
  • We observed it two days with some common pages. Typo3 4.5.25 was always faster, even if we cleared the cache some seconds before.

The Typo3-Core is linked via symlink, so we can switch easily between the two versions. The behaviour‎ was reproducible with each switch.

Actions #3

Updated by Alexander Opitz over 11 years ago

Can you check if there are temporary files that got written on every page request?

Actions #4

Updated by Webadmin no-lastname-given over 11 years ago

I can only see the normal lock-files in /typo3temp/locks. Do you have a special folder in mind?

An additional information: I just tried updating to 4.5.26 and there everythings works well. So the problem must be from .26 to .27.

Actions #5

Updated by Alexander Opitz over 11 years ago

And the typo3conf/temp* Files?

I'm more on 6.2 development, so I don't know what all changed in from .26 to .27

Actions #6

Updated by Alexander Opitz about 11 years ago

  • Is Regression set to No

Did something change with newer releases?

Updated by Webadmin no-lastname-given almost 11 years ago

Sorry for the delay. Today we updated to 4.5.32 and the result was the same. Attached you will find two screenshows from newrelic.com. At 13:35 we did the update.

After the update the cpu usage and load were much higher than with 4.5.26. Especially there was a hight number of GraphicsMagick processes. After some some minutes the number of processes decreased, but the page is still slow.

Actions #8

Updated by Webadmin no-lastname-given almost 11 years ago

In the meantime we discovered the reason for this problem. It is related to Bug #34446 which was fixed from version 4.2.26 to version 4.2.27.

We have a typoscript navigations on our page, which uses the GIF BUILDER and loads transparent PNGs. It seems, that typo3 tries to process these images on every page load.

After setting [GFX][png_truecolor] to true in the install tool the problem is gone.

Actions #9

Updated by Alexander Opitz almost 11 years ago

  • Status changed from Needs Feedback to New

Hmmm, thats why I asked if there are temporary files that got written on every page request. ;-)

Ok, this doesn't solve the real problem, but there is now a point to look.

Actions #10

Updated by Mathias Schreiber almost 10 years ago

  • Status changed from New to Closed

when rendering PNGs you should always set them to true_color

Actions

Also available in: Atom PDF