COMPARE / PACKVIUM VS PACKINGSOLVER
packvium vs packingsolver, measured on OR-Library.
packingsolver was Pareto-optimal in 3 of 3 profiles measured against packvium.
| Profile | packvium utilisation | packvium packed | packingsolver utilisation | packingsolver packed | Verdict for packingsolver |
|---|---|---|---|---|---|
| 3 item types · orlib-thpack-1 | 86.06% | 90.50% | 89.02% | 84.14% | Pareto-optimal |
| 12 item types · orlib-thpack-5 | 83.88% | 89.19% | 85.44% | 87.27% | Pareto-optimal |
| 20 item types · orlib-thpack-7 | 82.82% | 87.03% | 82.97% | 78.58% | Pareto-optimal |
HOW TO READ THIS
Two axes, and no blended score.
An engine is Pareto-optimal when nothing beat it on every axis at once. Runtime is recorded per run but is deliberately not an axis: one competitor only builds for linux/amd64 and runs under emulation here, so ranking that mixture would compare host arrangements rather than engines. Until a fair speed frontier is published, a fastest-engine claim is not one this project is entitled to make.
See every engine on every profile ↗