Profiling report resolution too low
When running criterion benchmarks under profiling, the criterion internals usually dominate the report. That means that the code you actually care about ends up with very low percentages:
individual inherited
COST CENTRE MODULE no. entries %time %alloc %time %alloc
...
Full Data.HashMap.Base 360 725180 0.2 0.5 0.4 0.9
Leaf/neq Data.HashMap.Base 364 5151 0.0 0.0 0.0 0.0
BitmapIndexed/update Data.HashMap.Base 362 227250 0.1 0.2 0.2 0.3
BitmapIndexed/insert Data.HashMap.Base 365 78376 0.0 0.0 0.0 0.0
Leaf/neq Data.HashMap.Base 363 132411 0.0 0.1 0.0 0.1
BitmapIndexed/insert Data.HashMap.Base 361 191597 0.0 0.1 0.0 0.1
BitmapIndexed/update Data.HashMap.Base 357 4545 0.0 0.0 0.0 0.0
BitmapIndexed/insert Data.HashMap.Base 359 3030 0.0 0.0 0.0 0.0
Leaf/neq Data.HashMap.Base 358 1515 0.0 0.0 0.0 0.0
BitmapIndexed/insert Data.HashMap.Base 356 1414 0.0 0.0 0.0 0.0
Leaf/neq Data.HashMap.Base 355 101 0.0 0.0 0.0 0.0
Empty Data.HashMap.Base 354 101 0.0 0.0 0.0 0.0
If you're interested in comparing the relative time spent in these functions, that's not really possible as these numbers have too low accuracy.
Trac metadata
Trac field | Value |
---|---|
Version | 7.6.3 |
Type | Bug |
TypeOfFailure | OtherFailure |
Priority | normal |
Resolution | Unresolved |
Component | Profiling |
Test case | |
Differential revisions | |
BlockedBy | |
Related | |
Blocking | |
CC | |
Operating system | |
Architecture |