RFC: JDK-8031043: ClassValue's backing map should have a smaller initial size

[Christian Thalinger]

On Jan 9, 2014, at 5:25 PM, Charles Oliver Nutter <headius at headius.com> wrote:

> It depends how JRuby is deployed. If the same code runs in every JRuby
> runtime, then there would be one value attached to a given class per
> runtime. Generally, this does not exceed a few dozen JRuby instances
> for an individual app, and most folks don't deploy more than a few
> apps in a given JVM.

Interesting.  Thanks for the information.

> 
> - Charlie
> 
> On Thu, Jan 9, 2014 at 1:16 PM, Christian Thalinger
> <christian.thalinger at oracle.com> wrote:
>> 
>> On Jan 9, 2014, at 2:46 AM, Jochen Theodorou <blackdrag at gmx.org> wrote:
>> 
>>> Am 08.01.2014 21:45, schrieb Christian Thalinger:
>>> [...]
>>>> If we’d go with an initial value of 1 would it be a performance problem for you if it grows automatically?
>>> 
>>> that means the map will have to grow for hundreds of classes at startup.
>>> I don't know how much impact that will have
>> 
>> If it’s only hundreds it’s probably negligible.  You could do a simple experiment if you are worried:  change ClassValueMap.INITIAL_ENTRIES to 1, compile it and prepend it to the bootclasspath.
>> 
>>> 
>>> bye Jochen
>>> 
>>> --
>>> Jochen "blackdrag" Theodorou - Groovy Project Tech Lead
>>> blog: http://blackdragsview.blogspot.com/
>>> german groovy discussion newsgroup: de.comp.lang.misc
>>> For Groovy programming sources visit http://groovy-lang.org
>>> 
>>> _______________________________________________
>>> mlvm-dev mailing list
>>> mlvm-dev at openjdk.java.net
>>> http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
>> 
>> _______________________________________________
>> mlvm-dev mailing list
>> mlvm-dev at openjdk.java.net
>> http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
> _______________________________________________
> mlvm-dev mailing list
> mlvm-dev at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev