diff options
author | Todd Gamblin <tgamblin@llnl.gov> | 2022-12-22 23:38:42 -0800 |
---|---|---|
committer | Harmen Stoppels <harmenstoppels@gmail.com> | 2022-12-26 22:28:44 +0100 |
commit | be6bb413dfed861c5f317b5d7274e4d47c34aeab (patch) | |
tree | 08771b638cb979dbfcd97b18b95013ece6659391 /.mailmap | |
parent | d23c302ca2e76c4a0f0ab4114d4132febdd1ff18 (diff) | |
download | spack-be6bb413dfed861c5f317b5d7274e4d47c34aeab.tar.gz spack-be6bb413dfed861c5f317b5d7274e4d47c34aeab.tar.bz2 spack-be6bb413dfed861c5f317b5d7274e4d47c34aeab.tar.xz spack-be6bb413dfed861c5f317b5d7274e4d47c34aeab.zip |
`spack solve`: use consistent units for time
`spack solve` is supposed to show you times you can compare. setup, ground, solve, etc.
all in a list. You're also supposed to be able to compare easily across runs. With
`pretty_seconds()` (introduced in #33900), it's easy to miss the units, e.g., spot the
bottleneck here:
```console
> spack solve --timers tcl
setup 22.125ms
load 16.083ms
ground 8.298ms
solve 848.055us
total 58.615ms
```
It's easier to see what matters if these are all in the same units, e.g.:
```
> spack solve --timers tcl
setup 0.0147s
load 0.0130s
ground 0.0078s
solve 0.0008s
total 0.0463s
```
And the units won't fluctuate from run to run as you make changes.
-[x] make `spack solve` timings consistent like before
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions