Basically users are free to place the measurement calls to their liking. This implies that bracketed measurement intervals can be defined overlapping even within a single thread, thereby accounting the overlapping time interval several times. However, for the time spent per thread, only actual thread activity should be counted, disregarding overlaps. Thus introduce a new aggregate, ''active time'', which is the sum of all thread times. As an aside, do not need explicit randomness for the simple two-thread test case — timings are random anyway... + bugfix for out-of-bounds access |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||