CodeTools proposal: "fjptrace"

[Aleksey Shipilev]

Any comments?

Thanks,
-Aleksey

On 01.07.2015 17:15, Aleksey Shipilev wrote:
> Tool Name:
> Java Fork/Join Trace (fjptrace)
> 
> Tool Purpose:
> Java Fork/Join Trace (fjptrace) is an instrumented ForkJoinPool
> implementation that produces the event trace, plus a set of trace
> visualizers.
> 
> Proposed By:
> Aleksey Shipilev, Oracle, Java SE Performance team
> 
> Rationale:
> Java Fork/Join Trace is a tool to understand the end-to-end behavior of
> java.util.concurrent.ForkJoinPool (FJP). It was a foundational tracing
> tool that exposed problems and outlined the solutions in FJP during the
> early Project Lambda work.
> 
> Since FJP became implicitly exposed to users as the executor for
> Parallel Streams in JDK 8, some users started to have problems following
> up on performance problems.
> 
> With fjptrace as part of the OpenJDK CodeTools Project, we can provide
> the tooling to let users introspect the FJP behavior, as well as produce
> the high-quality performance bug reports with the data backed up by
> fjptrace data.
> 
> Thanks,
> -Aleksey
>