summarize: Make incr-cache-loading and query-blocking contribute to self-time of query.

[michaelwoerister]

Adjusts the logic in summarize according to #75 (comment).

The differences in absolute numbers should be small. But it is more consistent, I think.

Fixes #75.

r? @wesleywiser

[michaelwoerister]

I might make sense to do a new release for this and switch perf.rlo over. It is the last thing missing for the MVP, I'd say.

[andjo403]

to me this looks good.
but maybe before a new release, something that you talked about in the issue was total time and maybe you are thinking the total time in chrome tracing where you have a self time and total time for an event and I think that is missing from showing all information for events. I also think that the total time is needed for e.g. in #67

[michaelwoerister]

@andjo403, I think what you are talking about I have seen being referred to as "inclusive" and "exclusive" times for an event. "Inclusive" would then also contain the time of child events. I think calling it "inclusive" and "exclusive" times is pretty good. Right now we only show "exclusive" times (what we call "self time"), adding a column for inclusive time to perf.rlo is a very good idea.

[michaelwoerister]

Hm, kCacheGrind and https://github.com/KDAB/hotspot call it "self" and "inclusive" times.

[wesleywiser]

Sorry for the delay on this. Looks great to me!

[wesleywiser]

The Chrome profile calls this "self time" vs "total time" FWIW