Allocations profiler

[Matt Warren]

> Sorry if this is nit-picking but it would be the allocators that would
track this.

Yeah good point, I got my terminology wrong :-)

Also thanks for the Java history lesson, it's interesting to learn about
things like that.

On 27 February 2015 at 07:05, Kirk Pepperdine <kirk at kodewerk.com> wrote:

>
> >
> > So I don't think it comes from a 3rd party profiler, but instead the
> > runtime itself. So I guess there's still some overhead, but it's
> > minimal as the go GC must have knowledge of allocations.
>
> Sorry if this is nit-picking but it would be the allocators that would
> track this.
>
> The tooling question for Java is interesting as this discussion about
> tooling goes back more than 20 years. It was never the intent of Sun to
> provide tooling for Java and they actively stayed out of the tooling arena.
> JMX was forced into the JDK (1.4 time frame by JRockit) as customers were
> demanding greater visibility. The VisualVM project was really frowned upon
> as it was seen as a threat to partners who were in the tooling space at
> that time. As you can see, Oracle as a completely different idea on tooling
> hence JMC and JFR.
>
> Regards,
> Kirk
>
>