debugging output

Brian Goetz brian.goetz at oracle.com
Tue Sep 25 09:29:29 PDT 2012


These are there as "tripwires" to identify when we're taking code paths 
we shouldn't be.  There are two kinds of tripwires currently:
  - When we have no parallel implementation of an Op, and fall back to 
serial;
  - When we instantiate a Mapping in a MapStream operation, instead of 
dealing directly on the (k, v) values.

We're currently at zero on the latter and I want to stay that way :)

We can redirect the output through an alternate PrintWriter that you 
could pipe to /dev/null for perf tests?

On 9/25/2012 5:07 AM, Aleksey Shipilev wrote:
> Hi guys,
>
> Can we drop the debugging messages from the current code? It generates a
> lot of garbage in our tests, like:
>
> FindFirstOp using ShortCircuitTerminalOp.computeParallel serial default
> FindFirstOp using ShortCircuitTerminalOp.computeParallel serial default
> ...(lots of times)...
> FindFirstOp using ShortCircuitTerminalOp.computeParallel serial default
>
> Granted, the test which print those messages should not be considered in
> their seriousness, but this impedes our operations here. Alternatively,
> we could guard that by the flag to print the message once per JVM run,
> like [1].
>
> -Aleksey.
>
> [1] http://shipilev.net/pub/jdk/lambda/printOnce.patch
>


More information about the lambda-dev mailing list