Project

General

Profile

Actions

Bug #19587

closed

Multiple image resizes started

Added by Vlatko Šurlan over 15 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Category:
Content Rendering
Target version:
-
Start date:
2008-11-10
Due date:
% Done:

0%

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

Description

When an image needs to be resized for a page to be displayed, if that page is reloaded the resize process will start one more time for each reload. This tends to bring to a grinding halt my tender pIII 800MHz web server. It would be nice if TYPO3 kept track of the images being resized and refused to start multiple resizes of the same image. This happens on my systems configured to use ImageMagick and I noticed this by using top which displayed a bunch of convert processes with the same image parameter.

(issue imported from #M9762)

Actions #1

Updated by Alban Cousinie over 15 years ago

Hello Vlatko,

Are you sure of what you say ? What elements do lead you to this conclusion ?

The default behavior when you add and image through a templavoila Flexform is that the image is resized once when the image is submited in the backend, then the resized image is copied somewhere inside the /uploads/ folder and the genuine image will no longer be used, only the pre-resized image will be served

With the old templating system, the images should be resized once the cache is emptied, then the image should be cached.

I'm not an expert with Typo3 internals, but this is the intended behavior. One possibility though is that you could be using some plugin which does live image resizing using GD or Imagemagick and this one would make your server crawl ?

Maybe this input could be helpful.

Actions #2

Updated by Vlatko Šurlan over 15 years ago

I think this is caused by some gallery, perhaps ce_gallery or such so it might be as you said that the extension is the issue. I cannot say for sure but it might be that the core would behave the same way. Not such a relevant issue I presume but still might be something to look into...

Actions #3

Updated by Susanne Moog almost 15 years ago

This seems to be caused by an extension as I can't reproduce the behavior with TYPO3 core (trunk 4.3-dev).

Actions #4

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF