RFR: 8175561: Memory churn in jimage code affects startup after resource encapsulation changes
claes.redestad at oracle.com
Thu Feb 23 22:57:36 UTC 2017
various resource encapsulation changes in 9+148 meant an uptick in
footprint and startup times for certain applications.
While some of this regression is hard to avoid (opening readers,
touching more memory mapped pages etc), a large part is due to simple
java allocation churn, some of which can be optimized away by reducing
the number of objects we create when scanning modules for resources.
 Things we could do in the future to improve further include adding
an index to the jimage (too late for 9) or marking modules with no
non-encapsulated resources as such so that they can be skipped.
More information about the jigsaw-dev