COMPARE / PACKVIUM VS 3DBINPACKING

packvium vs 3dbinpacking, measured on OR-Library.

3dbinpacking against packvium on the pinned OR-Library profiles: dominated in 3.

WHEN THIS WAS MEASURED · The sweep on this page ran against the 1.3.0 release on 2026-09-15, on a request set pinned on 2026-08-05. The raw artefacts per run are kept beside the baseline in benchmarks/results/COMPARATOR-BASELINE-1.3.0.md.

packvium vs 3dbinpacking
Profilepackvium utilisationpackvium packed3dbinpacking utilisation3dbinpacking packedVerdict for 3dbinpacking
3 item types · orlib-thpack-186.06%90.50%67.40%80.90%dominated
12 item types · orlib-thpack-583.88%89.19%53.29%75.61%dominated
20 item types · orlib-thpack-782.47%87.54%50.83%72.18%dominated
THE PROJECT ITSELF

Read from 3dbinpacking's own public repository and documentation, not from running its code - unlike the benchmark numbers above, which this project's own validator recomputes on every run.

Licence
MIT
Language
Python
Deployment
A Python library, added to a project's own dependencies.
Multiple containers per solve
Yes
Dependencies
A documented port of a Go implementation (gedex/bp3d); pure Python beyond that lineage.
Constraints modelled
Weight limits and item/bin sorting. Its documentation does not describe rotation or support restrictions.
Determinism
Not addressed beyond a configurable decimal precision for its own arithmetic.
Validation and refusals
Distributes items across bins to minimise unused space, but its documentation does not describe a reason for an item that was not placed.
Limitations
Python only, and its documentation does not describe rotation, stacking or support constraints.
Source: 3dbinpacking (2026-09-17)
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. Nothing on this page is a speed claim, and none should be read out of it.

See every engine on every profile