According to some older pprof tutorials, the units reported by "top" or "web" are the numbers of calls. Newer tutorials as well as my own experiments show seconds instead. For example, compare:
(pprof) top10 Total: 2525 samples 298 11.8% 11.8% 345 13.7% runtime.mapaccess1_fast64 268 10.6% 22.4% 2124 84.1% main.FindLoops 251 9.9% 32.4% 451 17.9% scanblock 178 7.0% 39.4% 351 13.9% hash_insert 131 5.2% 44.6% 158 6.3% sweepspan 119 4.7% 49.3% 350 13.9% main.DFS 96 3.8% 53.1% 98 3.9% flushptrbuf 95 3.8% 56.9% 95 3.8% runtime.aeshash64 95 3.8% 60.6% 101 4.0% runtime.settype_flush 88 3.5% 64.1% 988 39.1% runtime.mallocgc (taken from https://blog.golang.org/profiling-go-programs) with what I get: (pprof) top10 1780ms of 3640ms total (48.90%) Dropped 74 nodes (cum <= 18.20ms) Showing top 10 nodes out of 197 (cum >= 80ms) flat flat% sum% cum cum% 420ms 11.54% 11.54% 420ms 11.54% runtime.memmove 380ms 10.44% 21.98% 790ms 21.70% runtime.mallocgc 240ms 6.59% 28.57% 240ms 6.59% runtime.memclr 130ms 3.57% 32.14% 720ms 19.78% compress/flate.(*decompressor). huffSym 130ms 3.57% 35.71% 160ms 4.40% syscall.Syscall 120ms 3.30% 39.01% 120ms 3.30% runtime.procyield 100ms 2.75% 41.76% 100ms 2.75% crypto/aes.gcmAesDec 90ms 2.47% 44.23% 90ms 2.47% runtime.futex 90ms 2.47% 46.70% 90ms 2.47% runtime.heapBitsSetType 80ms 2.20% 48.90% 80ms 2.20% crypto/sha1.blockAVX2 1. Does the profiling unit depend on OS? 2. Was the profiling unit changed in the past from plain number of calls to time (seconds)? 3. Is it possible to force the unit to be the number of calls? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
