To clarify what you did...you deployed the application to the cluster
while the instances were down, and then the time for start-cluster on
the first start of the cluster was 65 seconds? That would seem to be
reasonable, as this start-cluster requires synchronizing the application
to all of the instances. The actual sync time depends on the network
bandwidth you have and the speed of your DAS, but 65 seconds would seem
reasonable for a 19MB application. I expect that if you stop the
cluster and restart it, the start time should go down, probably not to
the original 15 seconds, because the instances need to load the
application, but it should go down to something below 65 seconds.
Tom
On 9/23/2010 7:00 PM, Elena Asarina wrote:
> Hi,
>
> I've deployed to the 10-instances cluster one 19 Mb application. After
> that start cluster time changed from 15 seconds to 65 seconds. It it
> OK or not?
>
> Thank you,
>
> Elena
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>