TYPO3 Core

Exactly, this time-out is the problem.
Chances are the time-out comes from the db-server importing 20.000 records.
On hosted webspace you cannt set time out to 240 or even more.

Solution could be to send just the records still to update to the db-server
instead of sending the whole extensions list to the db-server again and again
from the very first record.

We do have the time of the last update, so it should be no problem to
see on update-php-scripts start whether to send the whole list of extensions
or just the remaining x records not yet in db-table.

Or to make sure by php that there is no
timeout by restarting db-update more than once when needed.
Or just sending xy records at a time and waiting for db-servers answers.

Not all hosted webspaces do allow script time-outs of 240 SECONDS or even more.
Saving more than 20.000 records in 240 seconds is a pretty good value for hosted db-servers!?

We got that working on shared hosting with execution times below 100 seconds. So the DB backend seems to be really slow on your side.

Still, I agree there's much room for improvement, but I've not time to dig into this code. Maybe you can?

Hey,

thanks for this report. The issue at this point is that the current import process of the extension list is already optimized pretty well and can't be changed without refactoring the whole thing on a structural level and with a lot of effort.

The max_execution_time is checked in the system within the install tool, the default system requirement of TYPO3 is to have 240 seconds execution time. This is done to mitigate the risk of such cases were a broken import will leave the extension manager with broken or incomplete data. Also, this limit is sometimes important for other time consuming tasks by the system.

At the moment, the sytems warns at a couple of places if this limit is ignored: The install tool shown this in the environment test, it is shown in the default screen that is rendered for admins after login. Furthermore, when installing the system on an environment that does not fit TYPO3 needs, a button "i know what i'm doing" has to be pressed.

At the moment, I tend to reject this issue with "won't fix" since there is no way to get rid of this longish import process currently, and any change here (eg. an incremental import based on ajax) puts the structure of the extension manager at risk and is very time consuming. We will not do that at the moment.