[TYPO3-performance] TS-Rendering - IMG_RESOURCE - 622 ms - Solution

[georg kuehnberger]

Martin Kutschker wrote:
> Steffen Kamper schrieb:
>> Hi,
>> and now? Big discussion but no result :(

Ahoi all,
upfront, sorry for coming late to the party ;-)

 >> and now? Big discussion but no result

I have to disagree.
Here's my personal summary so far:

- MartinH:
already found his "workaround", however it needs implementation.

- TYPO3-In-General:
There have been quite some excellent suggestions to handle MartinH's 
issue, and even some consense on the logic.
Me feels its now time to move this performance-defect towards the 
bugtracker and then we will find a patch for it. @MartingH: Guess you 
dare to file a report, right?

- IMHO: (the bigger picture)
The Generation of TYPO3's FE-HTML-Output (HTML - sic!)
is (partly uselessly) delayed by:

a) waiting for the generation of thumbs/resized versions of 
img-ressources in general and
a1) large ones especially.

b) re-checking (thumb & original) of already generated img-ressources 
for var. reasons.
b1) large ones especially.

Focusing on the main task, which is deliver HTML to the client ASAP,
neighter a) nor b) should be in the way - right?

Both a) & b) are server-tasks (handled by IM/GM /PHP/whomever) which 
should be handled without letting the client wait for HTML.
The only requirement (during page-generation) towards the client would 
be to deliver a link to an img-resource (or script/dispatcher eg. eID), 
which the client would request for "later on". The script would then 
deliver the requested image/file and would also take care of re-writing 
the "direct" links within the TYPO3 cach-tables.

I hope to find some time by the end of the year to dummy-implement a 
meaningful-file-handle-procedure avoiding the above for the DAM. DAM 
only because a) all mentioned requirements (file-sizes, number of files, 
performance) mainly match DAM-Instances and b) as Masi already mentioned 
I'd like to be able to "outsource" both: the generation and the storage 
of thumbnails. (eg. to EC2 & S3)

Looking forward,
regrads georgk