COMPARE / PACKVIUM VS 3D-BIN-CONTAINER-PACKING

packvium vs 3d-bin-container-packing, measured on OR-Library.

3d-bin-container-packing against packvium on the pinned OR-Library profiles: not applicable 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 3d-bin-container-packing
Profilepackvium utilisationpackvium packed3d-bin-container-packing utilisation3d-bin-container-packing packedVerdict for 3d-bin-container-packing
3 item types · orlib-thpack-186.06%90.50%——not applicable - all-or-nothing by construction: returns nothing rather than a best effort
12 item types · orlib-thpack-583.88%89.19%——not applicable - all-or-nothing by construction: returns nothing rather than a best effort
20 item types · orlib-thpack-782.47%87.54%——not applicable - all-or-nothing by construction: returns nothing rather than a best effort
THE PROJECT ITSELF

Read from 3d-bin-container-packing'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
Apache-2.0
Language
Java
Deployment
A Java library, published to Maven Central.
Multiple containers per solve
Yes
Dependencies
Maven-managed; no further dependency stated.
Constraints modelled
Rotation and weight limits (maximum load, empty weight); its own LAFF placement strategy orders boxes by volume first.
Determinism
Its documentation does not state whether a run is reproducible.
Validation and refusals
Ships a component named Validator, though its documentation does not detail what it checks. Success is a boolean; its documentation does not describe a reason per unplaced item.
Limitations
Java only, and its Apache-2.0 licence carries patent-grant and NOTICE terms the other five (all MIT) do not.
Source: 3d-bin-container-packing (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