Why True-Shape Nesting Is CPU-Heavy — and How Pressria Bridge Stays Fast on Modest Hardware

2026-05-29 · nesting true-shape performance

Ask anyone who has run true-shape nesting on a real production sheet and you'll hear the same thing: it's slow, and it gets dramatically slower as the part count climbs. That reputation is earned. But "slow" is a property of how the work is structured, not a law of nature — and the structure is something you can change. This is a look at why true-shape nesting is so CPU-heavy, and how Pressria Bridge stays fast enough to run on hardware a print shop already owns.

Why true-shape nesting is heavy in the first place

Rectangular packing is cheap: a part is just a bounding box, and fitting boxes together is fast. True-shape nesting is different. It works on the actual outline of each part, so it can tuck a curved keychain into the hollow of another instead of wasting the space around its bounding box. That tighter packing is the whole point — it's where the material savings come from — but it's expensive to compute.

The cost comes from two places. First, the core geometric operation — figuring out how close one irregular outline can sit next to another without overlapping — has to be evaluated across many pairs of parts, and the number of pairs grows fast as parts are added. Second, the cost of each of those operations scales with how detailed the outlines are: a contour described by thousands of points is far heavier to test than the same shape described by a few hundred. Put those together and a sheet with many detailed parts becomes a genuinely large computation. That's why the conventional answer has been to throw hardware at it.

Four identical triangular parts packed two ways. Bounding-box packing wraps each part in its own rectangle, leaving half of every box empty. True-shape packing interlocks two parts per rectangle, fitting all four in half the area.

The industry's default answer: buy a bigger machine

Look at the system requirements published by most dedicated nesting tools and a pattern appears — high core counts, large amounts of RAM, fast processors, all framed as prerequisites for handling complex jobs at acceptable speed. The logic is sound on its own terms: nesting is processor-intensive, so more processor means faster results. But it quietly accepts the computation as fixed and only scales the machine underneath it. For a mid-sized print shop, that turns "I want to automate my imposition" into "I need to buy a new workstation first."

There's another path that's easy to overlook: instead of making the machine bigger, make the computation smaller.

Pressria Bridge isn't one packing pass — it's a cascade

The biggest structural difference is that Pressria Bridge doesn't treat a sheet as a single brute-force packing problem. It runs the layout as a multi-stage cascade, where each stage does a specific job and hands a cleaner problem to the next:

Prepress simplification. Before any nesting happens, each part's outline is reduced to the smallest set of points that still represents its true shape. Since the cost of true-shape nesting scales with outline detail, cutting the detail cuts the work directly — the solver is doing the same job on far less geometry.
Group-aware placement. Real production sheets aren't a flat pile of parts; they're grouped — by order, by customer, by cut job. Pressria Bridge places parts as groups so an order stays together on the sheet instead of being scattered across it. This is something single-function packing tools generally don't do at all, and it matters as much for the shop floor as raw efficiency does.
True-shape placement. The main pass fits the simplified outlines together as tightly as the shapes allow.
Gap-fill. A first placement always leaves usable pockets between parts. A dedicated gap-fill stage goes back over the sheet and drops smaller parts into those pockets — recovering material that a single placement pass leaves on the table.

Pressria Bridge's nesting cascade: a raw sheet of many detailed parts passes through prepress simplification, group-aware placement, true-shape placement, and gap-fill, producing a tight, order-intact layout.

The point of the cascade isn't any one clever trick. It's that the heavy geometric work is only ever asked to solve a problem that earlier stages have already made smaller and cleaner. You get the tight packing of true-shape nesting and the order-integrity of group nesting, without handing the solver a needlessly enormous problem.

The result: it runs on hardware you already have

Because the computation itself is lighter, the hardware underneath it doesn't have to be top of the line. The same 600×400mm sheet that finishes in well under a minute on a current machine also completes in the low-80-second range on a Xeon E3-1230 v2 — a four-core CPU from 2012. Part counts vary with the size and shape of the parts on any given sheet, but the sheet size and the workload are the same; the only real difference is more than a decade of CPU generations.

For a print shop, that's the practical headline. Automating your imposition doesn't have to start with a hardware purchase. The PC already sitting on the prepress desk is very likely enough — which lowers the cost of adopting automation from "new workstation plus software" to just the software.