Lloyd L Chambers wrote:
> That is not correct. The AdminService is started in ApplicationServer
> as the very first ServerLifecycle module. It most defininitely is
> not started on demand.
>
> Much of what the AdminService does is required by other parts of the
> server. Disabling it would cause many other pieces to fail.
>
> I am working on threaded server startup, which includes the admin
> service. I am seeing a 40% reduction in startup time (real time) for
> a full startup (not quickstart).
Do you get a reduction in memory footprint also?
With quickstartup *and* threaded startup, do you get a
further reduction in startup time?
- Binod.
>
> Lloyd Chambers.
>
> On Dec 8, 2006, at 1:54 AM, Sanjeeb Kumar Sahoo wrote:
>
>> We seem to be initializing the admin service only on demand. Would
>> it be better to initialize it in the back ground as soon as the
>> server starts? How often will there be a server running where there
>> will be no administration activity? By not initializing admin
>> service, who are we optimizing it for?
>>
>> Thanks,
>> Sahoo
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>