New issue: run time eager module loading

[mark.reinhold at oracle.com]

2016/3/11 13:55:56 -0800, david.lloyd at redhat.com:
> On 03/11/2016 11:47 AM, mark.reinhold at oracle.com wrote:
>> 2016/3/2 19:22 -0800, david.lloyd at redhat.com:
>>> ...
>>> 
>>> Can there not instead be an incremental resolution algorithm, akin to
>>> how classes are lazily loaded?
>> 
>> Configuring a set of modules and instantiating that configuration as a
>> layer requires no more than reading the modules' descriptors.  Nothing
>> else from any module definition will be read until it's actually needed.
> 
> But it does require that all the module descriptors from a given layer 
> be available, and that the load time for the first load of a module in a 
> layer will always be bounded by the size of the layer, rather than just 
> by the dependency subgraph of the module being loaded.  Based on 
> application server deployments that I know about, I think the far upper 
> bound for a realistic number of modules in a layer will probably lie in 
> the thousands to ten thousands range (though there is always the outlier 
> case where someone has to push it to see how far it goes...), which 
> might translate into a substantial startup overhead.

New issue: http://openjdk.java.net/projects/jigsaw/spec/issues/#LazyConfigurationAndInstantiation

- Mark