[ http://jira.magnolia.info/browse/MAGNOLIA-1667?page=comments#action_14985 ] Grégory Joseph commented on MAGNOLIA-1667: ------------------------------------------
Actually, out of 90 tasks needed for a complete install (current trunk), only 18 take longer than 100ms to execute, and just 3 are above 1sec (bootstrapping lots of data). These figures are not taking the repository save operations into account, but still make 3sec refresh seem reasonable to me. You should try the latest trunk, which shows a counter of how many tasks have been executed (with the total to be executed)... seems like 10 seconds or more would be too "slow" with regard to the progress that's actually made in 3 seconds. WDYT? :) > Updatemech : the whole process should be running in a separate thread > --------------------------------------------------------------------- > > Key: MAGNOLIA-1667 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1667 > Project: Magnolia > Issue Type: Improvement > Components: updatemechanism > Reporter: Grégory Joseph > Assigned To: Grégory Joseph > Fix For: 3.1 > > > Threading: the whole process should happen in a separate thread rather than > during the request. This would help avoiding time outs and conflicts. (any > access to the page, once the process is started, would just display the > current state, i.e the list of tasks which have been executed, for instance) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
