And another question - where can I find implementation code for that getThreadAllocatedMemory1 ? The reason I am asking is that I see that calling this code does take some time (our request time grown under peak load with that function). While the growth is not substantial I am curious to understand the reason why this getThreadAllocatedMemory1 method takes time.
On Wednesday, February 7, 2018 at 11:17:39 AM UTC+2, Maxim Terletsky wrote: > > Well, for recording allocations in alloc mode. Why didn't you want this > size? > > On Tuesday, February 6, 2018 at 7:11:23 PM UTC+2, Andrei Pangin wrote: >> >> ¯\_(ツ)_/¯ >> >> Just don't know how it should be used. >> >> вторник, 6 февраля 2018 г., 14:54:48 UTC+3 пользователь Maxim Terletsky >> написал: >>> >>> One more question - why the original AsyncProfiler does not use >>> tlab_size in this method we talking about? >>> >>> https://github.com/jvm-profiling-tools/async-profiler/blob/master/src/allocTracer.cpp#L65 >>> >> -- You received this message because you are subscribed to the Google Groups "mechanical-sympathy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
