I have been experimenting a jlink plugin to improve the module system startup
time. On a Quad-Core Intel Xeon E5 @3.7 GHz, 16G memory (Mac Pro) machine,
the module system startup takes 110 ms and 75% of it is to reconstitute 64
module descriptors with 2388 packages altogether.
This high overh
Hi Mandy,
On 2015-10-05 23:13, Mandy Chung wrote:
I have been experimenting a jlink plugin to improve the module system startup
time. On a Quad-Core Intel Xeon E5 @3.7 GHz, 16G memory (Mac Pro) machine,
the module system startup takes 110 ms and 75% of it is to reconstitute 64
module descri
On 06/10/2015 12:38, Claes Redestad wrote:
Alternatively, wouldn't it be possible for the plugin to modify the
module-info.class directly?
Generating the classes at link time is about eliminating the need to
parse the module-info and reconstitute the module descriptors via the
builder API. Th
I realize I missed the attachment after seeing Claes’ question. This includes
the heap usage after GC.
> On Oct 5, 2015, at 2:13 PM, Mandy Chung wrote:
>
> I have been experimenting a jlink plugin to improve the module system startup
> time. On a Quad-Core Intel Xeon E5 @3.7 GHz, 16G m
See http://cr.openjdk.java.net/~mchung/jigsaw/jake-startup.20151005.pdf
Mandy
p.s. In fact the attachment got trimmed.
> On Oct 6, 2015, at 7:31 AM, Mandy Chung wrote:
>
> I realize I missed the attachment after seeing Claes’ question. This
> includes the heap usage after GC.
>
>
>
>
>
>
> On Oct 6, 2015, at 4:38 AM, Claes Redestad wrote:
>
> Hi Mandy,
>
> On 2015-10-05 23:13, Mandy Chung wrote:
>> I have been experimenting a jlink plugin to improve the module system
>> startup time. On a Quad-Core Intel Xeon E5 @3.7 GHz, 16G memory (Mac Pro)
>> machine, the module system s
Thanks!
This looks much better than I naively expected, especially w.r.t.
footprint, and I probably wouldn't have asked/suggested what I did if
I'd gotten the attachement the first time around (although I'd prefer
some native memory measurement over "heap-after-GC", this should be
indicative
