DM-33331: Monitor memory usage at select steps of BPS submission

[mxk62]

Checklist

• ran Jenkins
• added a release note for user-visible changes to doc/changes

[codecov]

Codecov Report

Merging #112 (e453de1) into main (63a1f4f) will increase coverage by 0.34%.
The diff coverage is 99.13%.

@@            Coverage Diff             @@
##             main     #112      +/-   ##
==========================================
+ Coverage   91.51%   91.86%   +0.34%     
==========================================
  Files          38       40       +2     
  Lines        2417     2532     +115     
==========================================
+ Hits         2212     2326     +114     
- Misses        205      206       +1     

Impacted Files	Coverage Δ
tests/test_usage.py	96.15% <96.15%> (ø)
python/lsst/utils/timer.py	96.96% <100.00%> (+0.70%)	⬆️
python/lsst/utils/usage.py	100.00% <100.00%> (ø)
tests/test_timer.py	99.48% <100.00%> (+0.16%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 63a1f4f...e453de1. Read the comment docs.

[ktlim]

Please fix the ticket number in the PR title. (While the branch appears correct, I think some tools rely on the title.)

[mxk62]

@ktlim Fixed.

[timj]

Many of my comments are about reorganizing things as mentioned on the BPS review. I also think that the log output for time_this can be simplified.

One other thing that we might want to do is to remove the getrusage call out of logInfo and move that into the new usage.py. If you make it return a DataClass with all the entries that logPairs uses and then the get_peak_usage could either disappear or else call that and unpack the information from the DataClass.

[timj]

Looks great. Some minor comments.