On Wed, Sep 2, 2009 at 2:21 AM, fabb...@google.com wrote:
Also, each TreeLogger branch is automatically timed, from start to when
we can figure the branch is dead (i.e. to first log emission NOT on the
branch, a slightly too exapansive definition.)
That isn't going to work in general --
That's a drag... I hadn't noticed any instances where the main log and child
were interleaved (do we bother to differentiate which parallel child logs
are being used, in such a case?? OOPHM clearly has multiple loggers going,
but it had seemed that within each we had fairly clean separation).
I think I'd rather look at any such work as orthogonal perf metrics data
gathering since it is really is, functionally, an independent question of
the log level. For example, we might want to see the effect of logging
itself on the speed of hosted mode refresh.
I think some sort of separate global
