homepage

When running pstats with functions that take less than 0.5 millisecond (per call for example), the value shown is '0.000, which isn't really helpful.
This patch aims to show the value in microseconds instead of seconds for values that would otherwise be displayed as '0.000'
(the display may have to be tweaked for non-utf8 users, as the μ character is used)
Example output:
 ncalls tottime percall cumtime percall filename:lineno(function)
 9827 0.007 7μs 0.007 7μs {method 'get' of 'dict' objects}
 3427 0.009 25μs 0.017 49μs {map}
 10701 0.006 5μs 0.006 5μs {method 'lower' of 'str' objects}
 31410 0.045 14μs 0.045 14μs {method 'split' of 'str' objects}
 10023 0.006 6μs 0.006 6μs {_weakref.proxy}
 31801 0.009 2μs 0.009 2μs {len}
 3892 0.003 7μs 0.003 7μs {method 'extend' of 'list' objects}
 1397 0.001 8μs 0.001 8μs {method 'replace' of 'str' objects}
 10488 0.010 9μs 0.010 9μs {method 'string_literal' of '_mysql.connection' objects}
 10702 2.620 2447μs 2.620 2447μs {method 'readline' of 'file' objects}
 10023 0.004 3μs 0.004 3μs {method 'info' of '_mysql.connection' objects}
 10023 0.005 5μs 0.005 5μs {method 'insert_id' of '_mysql.connection' objects}
 14327 0.022 15μs 0.022 15μs {method 'rstrip' of 'str' objects}

Hum, "2447μs" makes the output more difficult to parse (by a program) and to read (by a human). Why not always displaying 6 digits (after the dot) for the two "percall" columns.

I figured we didn't want to change the size of the columns (+12 COL), but this could easily be done yes

I concur with Victor. This change likely breaks graphical viewers of pstat data.
How gprof and similar tools solve the problem of outputting sub-millisecond timings?

> I concur with Victor. This change likely breaks graphical viewers of pstat data.
I propose to *do* break the format by always displaying percall timings with a precision of 6 digits.

Based on the review comments, it looks like the existing PR 3931 needs to be revised and resubmitted against current master branch. So, can we close PR 3931?