ci(codspeed): pin polars to one thread in the memory job - #980
Conversation
Build cost — v1 vs legacyv1 build peak & time relative to legacy, on this commit — not a comparison against master (that is CodSpeed).
Full table (time + peak, mean)📊 Interactive plots + CSV: download the semantics-report-v1-vs-legacy artifact from this run. Report-only · not a gate · refreshed on every push · obsolete once legacy is dropped. |
Merging this PR will regress 1 benchmark
Warning Please fix the performance issues or acknowledge them on CodSpeed. Performance Changes
Tip Investigate this regression by commenting Comparing Footnotes
|
Note
The following content was generated by AI.
Sets
POLARS_MAX_THREADS=1on the CodSpeed memory job.Polars allocates native memory per worker thread, so the peak memory of the polars-based benchmarks (e.g.
test_to_lp) depends on the core count of theubuntu-latestrunner. That produced a false regression on #974 (test_to_lp[nodal_balance-severity=0], 3.3 → 3.7 MB), for a legacy dense model that the PR's code does not touch.Measurements (master 38fbd4a vs feat/csr-boundaries a817a5e, write_lp only)
POLARS_MAX_THREADS=1: peaks and total allocations identical byte for byte across revisions and repeated processes.The walltime job is left untouched, since thread parallelism there is part of what is measured.