Re-measure coarse-allocation MILP solve time and its hardware impact - #90
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Redoes the
constant-alloc(coarse-allocation) experiments behind the "Speeding up MILP" subsection, whose numbers were stale.What was run
ckpt compile milpfor all 13 evaluated benchmarks at 5/10/50 uF, with and without--coarse-allocation(78 compiles, serial, to keep solve times clean) ->baseline_*.csv,coarse_*.csv,summary_*.csv.ckpt bench milpon hardware for the 9 benchmark x capacitor pairs where coarse changes the solution, in both modes and with/without device-debug ->hw/.Results
Geometric mean solve-time reduction: 25.0% at 5 uF, 23.8% at 10 uF, 28.8% at 50 uF (previously reported as 31.6 / 26.2 / 34.2%).
Worst case is now 77.3 s -> 66.5 s on
sensor_fusionat 5 uF, not the 5.1 s -> 2.6 s in the current text.The claim that coarse mode leaves boundary placement and memory allocation unchanged no longer holds: 9 of 39 pairs differ. On hardware, 8 of those 9 run no slower than the per-region solution (up to 2.6% faster);
cuckoo_filterat 5 uF is 3.5% slower.Notes
results/milp.csvto within 0.04%, so no other measured results are stale.rsaat 50 uF alternates between 8 and 9 boundaries across runs in coarse mode (equal-objective solutions); execution time is unaffected.milp_solve_time_msis rounded to whole milliseconds, so the seven pairs solving in 1-5 ms contribute quantization noise to the geomeans.