TraceTypeProfile as diagnostic option

[Aleksey Shipilev]

On 09/11/2012 01:21 AM, Vladimir Kozlov wrote:
> Aleksey Shipilev wrote:
>> Aha, are you suggesting this can jitter the memory footprint? Even if it
>> does, then you have the problem with memory footprint jitter, not with
>> the changes knocking you out of the beloved equilibrium.
>>
>> I think you want these (in bytes)?
>>  7418024 linux-baseline/j2re-image/lib/i386/client/libjvm.so
>>  7418057 linux-tracetype/j2re-image/lib/i386/client/libjvm.so
> 
> You changed only C2 code which is only in Server VM. Different size
> could be caused by different length of build path ("linux-tracetype" vs
> "linux-baseline").
> 
>> 11706683 linux-baseline/j2re-image/lib/i386/server/libjvm.so
>> 11706781 linux-tracetype/j2re-image/lib/i386/server/libjvm.so
> 
> Yes, this is what I would expect, about 100 bytes increase. But, please,
> try with the same build path length.

Actually, I had renamed the build *after* the build completes. So, these
two guys should have similar build paths (i.e. build/linux-i586/...).

-Aleksey.