[concurrency-interest] Fork/Join traces: instrumentation and rendering

Doug Lea dl at cs.oswego.edu
Sun Jun 17 16:39:01 EDT 2012

On 06/17/12 11:21, Aleksey Shipilev wrote:
> On 06/11/2012 01:10 AM, Doug Lea wrote:
>> Thanks to Aleksey for making the profiler available!
>> It is, among other things, a helpful tool for showing
>> the impact of these kinds of design decisions.
> FYI, I had pushed fjp-trace to GitHub [1].


> Additionally, I had pulled in vanilla JSR166 FJP into jsr166 branch, so
> one can see the changes between baseline and instrumented FJP by
> comparing the branches [2]. Doug, can you consider merging
> instrumentation code directly into JSR166?

I/We don't see a way to do it with zero guaranteed impact vs
non-instrumented code. But after giving fjp-trace some time to
settle in, we'll find some reasonable way to semi-integrate
to make it easier to use for diagnostics.


> [1] https://github.com/shipilev/fjp-trace
> [2] https://github.com/shipilev/fjp-trace/compare/jsr166...master

More information about the Concurrency-interest mailing list