RFR: Allocation latency tracing
Roman Kennke
rkennke at redhat.com
Thu Aug 24 15:12:08 UTC 2017
Am 24.08.2017 um 16:48 schrieb Aleksey Shipilev:
> On 08/24/2017 04:38 PM, Roman Kennke wrote:
>> I wonder if the tracing should be moved to the single place where we do
>> allocations (allocate_memory() ) instead of scattering around to all the
>> callers (mem_allocate(), allocate_new_tlab(), allocate_new_gclab() etc) ?
> Oh yes, silly me:
> http://cr.openjdk.java.net/~shade/shenandoah/stats-alloc/webrev.03/
>
>
>> In the long term (not this patch) all alloc-related code should be moved
>> to a separate class, either ShenandoahAlloc or even just ShenandoahFreeSet.
> Yup, having this tracing is the prerequisite for alloc-related code refactoring.
>
> Thanks,
> -Aleksey
>
>
Yes!
More information about the shenandoah-dev
mailing list