Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Evaluate measured cputime using the tests from github.com/golang/go/issues/36821, which demonstrate the inaccuracy and imprecision of go's 100Hz cpu profiler. The results here suggest that measured cputime is both accurate and precise with regards to computing on-CPU time. === RUN TestEquivalentGoroutines 0's got 9.98% of total time 1's got 9.53% of total time 2's got 9.22% of total time 3's got 10.42% of total time 4's got 9.84% of total time 5's got 10.43% of total time 6's got 10.50% of total time 7's got 10.21% of total time 8's got 10.03% of total time 9's got 9.86% of total time === RUN TestProportionalGoroutines 0's got 1.87% of total time (1.000000x) 1's got 3.60% of total time (1.931999x) 2's got 5.41% of total time (2.899312x) 3's got 7.21% of total time (3.864451x) 4's got 9.11% of total time (4.880925x) 5's got 10.94% of total time (5.864723x) 6's got 12.77% of total time (6.842004x) 7's got 14.34% of total time (7.685840x) 8's got 16.58% of total time (8.885060x) 9's got 18.18% of total time (9.741030x)
- Loading branch information