[TYPO3-dam-devel] RFC #10574: Speedup indexing when max_execution_time = 0

Dan Osipov dosipov at phillyburbs.com
Mon Mar 2 17:04:01 CET 2009


+1 from reading & testing, although I didn't see a significant 
improvement in indexing speed (LAN installation, max_execution_time = 0):
Prior to patch: 264 files indexed in 83 sec.
After the patch: 264 files indexed in 82 sec.

Dan Osipov
Calkins Media
http://danosipov.com/blog/

Steffen Gebert wrote:
> Hi list,
> 
> This is a SVN patch request.
> 
> Extension: dam_index
> 
> Branches: dam_1-1 / trunk
> 
> Type: Bugfix
> 
> Reference: http://bugs.typo3.org/view.php?id=10574
> 
> Problem:
> DAM indexing reloads frame after a runtime of 2/3 of max_execution_time to 
> avoid webserver killing the process.
> 
> If max_execution_time is set to 0 (=no limit), each file during indexing 
> causes a new HTTP request.
> $max_execution_time = ini_get('max_execution_time');
> $max_execution_time = intval(($max_execution_time/3)*2);
> $this->indexEndtime = time()+$max_execution_time;
> 
> Solution:
> We should use e.g. 60 sec if max_execution_time is 0 to speedup indexing of 
> larger amounts of files using slow network connections.
> 
> Regards
> Steffen
> 
> 


More information about the TYPO3-team-dam mailing list