We'll likely prioritize correctness over speed in gh-615 (which makes sense). Moving forward, we may want to add asv benchmarks, possibly with synthetic data until https://github.com/darshan-hpc/darshan-logs/issues/15 is resolved, and check for any low-hanging performance fruit.
I was reminded of this by this comment related to log file e3sm_io_heatmap_and_dxt.darshan (emphasis mine):
I'm no longer seeing any errors and can generate a summary report for that log with using this branch (it does take a couple of minutes).
We'll likely prioritize correctness over speed in gh-615 (which makes sense). Moving forward, we may want to add
asv
benchmarks, possibly with synthetic data until https://github.com/darshan-hpc/darshan-logs/issues/15 is resolved, and check for any low-hanging performance fruit.I was reminded of this by this comment related to log file
e3sm_io_heatmap_and_dxt.darshan
(emphasis mine):