Hi Grégory,
Thanks for the reply. You are right about the messages shown on the screen
("n of m tasks executed"). The counter usually reaches the maximum very
quickly (n=m), but then the waiting starts. The version handler now always
installs all files, that together are +/- 1Mb big.
I attach the code for the version handler as it is now. For the last upgrade
I only needed to bootstrap the dialog and paragraphs, not the menu and the
templates. Of course when the application is installed freshly (in an empty
database), I must make sure that the getExtraInstallTasks() method returns
ALL 4 tasks, not only the ones that were necesarry for the latest version
update. Am I right?
Best regards, Bert
http://www.nabble.com/file/p22060283/AssetModuleVersionHandler.java
AssetModuleVersionHandler.java
gregoryjoseph wrote:
>
>
> Hi Bert,
>
> Five minutes seems *very* long if all that happens is bootstrapping a
> few nodes. Usually, if you see "n of n tasks executed" and the screen
> still being reloaded for a little while, it's because the repository
> is being saved, which can indeed be a time consuming process. This is
> something we want to fix. [1]
>
> Now, to make this faster, it would probably help if you had a version
> handler that would take care of only updating the necessary nodes/
> property, thus making the save operation much faster. You give no
> details about your version handler, so there's nothing more I could
> say without wild guessing ;)
>
> Cheers,
>
> -g
>
> [1] http://jira.magnolia-cms.com/browse/MAGNOLIA-1855
>
> On Feb 17, 2009, at 8:56 AM, Bert Leunis wrote:
>
>>
>>
>> Dear Magnolians,
>>
>> Several times now I noticed this tiny problem, which I will
>> describe, and
>> which you can hopefully explain.
>>
>> For one of our clients we pack templates, dialogues and paragraphs
>> into a
>> module. When anything changed in these, the module gets a new
>> version, and
>> is bootstrapped again at deployment time. At the moment we are using
>> magnolia version 3.5.4 for this client.
>>
>> After starting the server, the installer screen comes up, and shows
>> that the
>> module is to be bootstrapped. Then I see INFO messages in the log
>> that tell
>> that the bootstrap files are installed. Next I have to wait 5
>> minutes for
>> the "Start up Magnolia" button to appear.
>>
>> Can you tell me what is going on in that time? I have no clue at
>> all. Is it
>> rebuilding indexes? My main question is: what can I do to get this
>> time as
>> short as possible?
>>
>> Thanks in advance,
>> Bert Leunis
>> --
>> View this message in context:
>> http://www.nabble.com/long-time-between-bootstrap-of-module-and-startup-magnolia-tp22052325p22052325.html
>> Sent from the Magnolia - User mailing list archive at Nabble.com.
>>
>>
>> ----------------------------------------------------------------
>> For list details see
>> http://www.magnolia-cms.com/home/community/mailing-lists.html
>> To unsubscribe, E-mail to: <[email protected]>
>> ----------------------------------------------------------------
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
>
>
>
--
View this message in context:
http://www.nabble.com/long-time-between-bootstrap-of-module-and-startup-magnolia-tp22052325p22060283.html
Sent from the Magnolia - User mailing list archive at Nabble.com.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
