Instrumented profiling for multimodule Jigsaw startup

Aleksey Shipilev aleksey.shipilev at gmail.com
Wed Mar 14 15:16:11 PDT 2012


On Thu, Mar 15, 2012 at 1:50 AM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
> On 14/03/2012 18:59, Aleksey Shipilev wrote:
>>
>> :
>>
>>   B. The major performance hog is reading module configuration. Even in
>> warm mode, it takes around 500ms to load local class map. It seems to be
>> connected with the size of it. I'm not sure if compressing will help
>> here, will explore a bit more.
>>
> Thanks for the data. Yes, the configuration loading is a bit embarrassing
> and hopefully should be addressed soon.

The thing I missed from explanation there: if you churn those 500ms
local class map loading out of 600ms of total startup time,
modularized Jigsaw startup is on-par with "legacy" JDK8 startup for
HelloWorld tests. Do you want me to see what could be addressed in
configuration, or is it someone else's part already?

-Aleksey.



More information about the jigsaw-dev mailing list