RFR(XS): Use lock version memory allocator
Zhengyu Gu
zgu at redhat.com
Mon Feb 27 16:21:41 UTC 2017
I ran Derby a couples of time on my machine , it is slightly better, but could just be a noise.
-Zhengyu
On 02/27/2017 11:19 AM, Roman Kennke wrote:
> Oh. I should have looked further ;-)
>
> OK then.
>
> Does it make a difference perf-wise?
>
> RomanAm 27.02.2017 5:17 nachm. schrieb Zhengyu Gu <zgu at redhat.com>:
>> That's why ShenandoahHeapRegion has to override it.
>>
>> -Zhengyu
>>
>>
>> On 02/27/2017 11:16 AM, Roman Kennke wrote:
>>> If I remember correctly, this throws asserts in debug mode. It wants an acquired Heap_lock.
>>>
>>> RomanAm 27.02.2017 5:12 nachm. schrieb Zhengyu Gu <zgu at redhat.com>:
>>>> Use lock version of heap region memory allocator.
>>>>
>>>> Webrev: http://cr.openjdk.java.net/~zgu/shenandoah/memory_allocate/webrev.00/
>>>>
>>>> Test:
>>>> fastdebug/release jdk: specjvm Derby
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> -Zhengyu
>>>>
More information about the shenandoah-dev
mailing list