placement utilization
Imagine the core of your chip as a parking lot and your standard cells as cars. Placement utilization just answers: how full is the lot? It's the fraction of the available floor that your logic actually occupies — add up the area of every standard cell and divide by the area of the core region they're allowed to sit in. A utilization of 0.70 means 70 percent of the floor is cells and 30 percent is still open asphalt.
That empty 30 percent is not waste; it's the breathing room the router needs. Wires don't travel in a separate dimension — they run on metal layers stacked above the cells, and they need to drop down through vias to reach cell pins, so a floor packed wall-to-wall with cells leaves nowhere to thread the connections. Push utilization too high — past roughly 80 to 90 percent — and the router runs out of tracks, congestion spikes, and you get unroutable nets or a flood of DRC violations. That's why early floorplans usually target a comfortable 60 to 70 percent: you're deliberately leaving slack so that clock-tree buffers, hold-fixing cells, and late ECO changes all still have somewhere to land before routing and signoff.
It helps to be precise about which area you're dividing by. Utilization is measured against the core (the placeable region), not the whole die — the die also carries the I/O pad ring and margins, which aren't yours to fill. And when big hard macros (memories, PLLs) or placement blockages sit in the core, tools often report an effective utilization against the area that's actually left for standard cells, which can read much higher than the raw number you first set.
The basic ratio — keep it well under 1.0 so the router has tracks to work with.
Utilization is a moving target, not a fixed dial: it creeps up through the flow as CTS adds clock buffers and timing fixes add cells, so leave headroom in the floorplan rather than starting near the ceiling.