3 ms·
It's worth noting that the first number in a benchmark result is how many loops (for n := 0; n < b.N) that Go used to find the results. The nanoseconds, bytes,
by Xeoncross 9y ago
It's worth noting that the first number in a benchmark result is how many loops (for n := 0; n < b.N) that Go used to find the results.
The nanoseconds, bytes, and allocs per operation are the important part.