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

[Steffen Kamper]

Hi,

Ernesto Baschny [cron IT] schrieb:
> Martin Kutschker wrote: on 29.06.2009 15:08:
>>> any hint?
>> No, but that reminds me of the idea we had to render the images in
>> separate HTTP connections so that the main page rendering isn't blocked
>> by image generation.
> 
> That would be an interesting project. Maybe even possible then to have
> the picture delivery and generation done by a "second" server
> (http://images.domain.example):
> 
> - Server A renders the page, IMAGE cObject returns the "filename" (with
> unique hash). It places information about how to generate the file (e.g.
> IMAGE configuration) in some shared cache.
> 
> - Server B gets request for the filename, which does not yet exist.
> Apache redirects request to TYPO3 (mod_rewrite required...), which will
> look up the shared cache, generate the image and return it.
> 
> This also could have been the same server, but different HTTP-processes,
> as Masi proposed. I like it!
> 

+1 for this. We used subdomain only for having shorter urls for images, 
but different HTTP-process would be nice.
Isn't that possible with an own page type? I fear not sufficient enough.

Any starts of doing this or only brainstorming?

vg Steffen