JEP 331: Low-Overhead Heap Profiling

[Martijn Verburg]

Hi Jeremy,

Yes we think it will cover our use cases.  Our workflow is currently either
to manually attach an agent or dynamically attach an agent with
functionality similar to https://github.com/google/allocation-instrumenter
(I suspect you know that well!). The dynamic one if some sort of SLA has
been breached.  It's our idea of a light-weight (as much as you can) on
demand allocation profiler.

It's just the dynamically attaching agent use case that will no longer work
for us (separate issue modularity / security), although the impact of that
is now also lessening as our customers will become more comfortable having
a permanent Java agent if it only does light weight things (one of our USPs
is being more lightweight than traditional 'gather all of the data all of
the time' approaches).

All in all this JEP seems really well designed to us, we just need to go
attack some real world use cases with it.


Cheers,
Martijn

On 3 April 2018 at 18:07, Jeremy Manson <jeremymanson at google.com> wrote:

>
> Thanks!  No problem about the source status - just curious about the use
> cases. That general kind of thing should be pretty easy to do without
> bytecode rewriting with this JEP.  Have you taken a close enough look at
> the current state of it to figure out whether it does what you want?
>
> Jeremy
>
> On Tue, Apr 3, 2018 at 3:17 AM Martijn Verburg <martijnverburg at gmail.com>
> wrote:
>
>> Mainly closed source (sadly) tooling for jClarity customers.  e.g.
>> Various object allocation probes that can be byte code weaved in to detect
>> and capture 'interesting' allocation patterns (such as humungous objects).
>>
>> Cheers,
>> Martijn
>>
>> On 3 April 2018 at 00:04, Jeremy Manson <jeremymanson at google.com> wrote:
>>
>>> Hey Martijn,
>>>
>>> That's an interesting response.  What did you build in this area?
>>>
>>> (In developing this project, we've been pretty focused on our use cases,
>>> many of which have been around for a very long time, so I'm really
>>> interested to see what others are coming up with.)
>>>
>>> Jeremy
>>>
>>> On Mon, Apr 2, 2018 at 1:40 PM Martijn Verburg <martijnverburg at gmail.com>
>>> wrote:
>>>
>>>> This is a very welcome advancement - thank you!  More NIH / custom LOC
>>>> to
>>>> be removed from various projects I'm on :-)
>>>>
>>>> Cheers,
>>>> Martijn
>>>>
>>>> On 29 March 2018 at 19:12, <mark.reinhold at oracle.com> wrote:
>>>>
>>>> > New JEP Candidate: http://openjdk.java.net/jeps/331
>>>> >
>>>> > - Mark
>>>> >
>>>>
>>>
>>