What does early congestion mean?
From PDVerse PnR Interview Handbook, part of the pdVerse Mentor Guide
Short Answer
Early congestion estimation is a rough, pre-route sanity check: it compares how much routing demand (nets that need to cross a region) exists against how much routing capacity (actual track resources) is available, in coarse rectangular regions across the chip. The clearest analogy is a highway system: the average traffic flow across the whole city can look totally fine while one specific junction is completely gridlocked — congestion is fundamentally a local phenomenon, and averaging it away at the chip level hides the real problem.
Technical Explanation
- "Overflow" is the specific signal to watch for: it means demand exceeds capacity on at least one routing resource in that region — more nets want to cross than there's room for at the available layers/directions.
- A lot of factors feed local demand and capacity that aren't obvious at first glance: routing direction (horizontal vs. vertical availability differs by layer), how many layers are actually usable in that region, macro edges (which block routing entirely), pin density (lots of pins crammed into a small area create local hotspots), wide buses (many parallel nets needing the same direction at once), power/ground reservation eating into signal capacity, and placement blockages.
- Because congestion is local, the fix is also local — you don't globally spread the whole design just because one corner is tight; you diagnose what's specifically causing that one region's demand/capacity imbalance.
- This is purely an early estimate, built before detailed placement and routing are final — it's meant to catch structural problems (a floorplan that's fundamentally too tight somewhere) before you sink hours into a routing attempt that's doomed from the start.
Visual Verification
Routing congestion occurs when signal interconnect demand exceeds available metal track capacity in a Global Routing Cell (GRC), leading to timing degradation and DRC shorts.
Formula Or Decision Rule
Decision rule: use the same early-routing method for alternatives and investigate local hot spots, not only averages.
What To Check
- Warning sign: Average congestion is acceptable but a macro corner or channel has overflow.
- Inspect: choose one affected region, macro, row, pin, path, or net and trace the physical cause.
- Correct: Confirm inputs, inspect the hot spot, change the cause, and rerun the identical estimate.
Command Checks & Actions
- route_global -floorplan true -congestion_map_only true: runs an early floorplan global-route estimate
report_congestion-mode summary: reports routing demand, capacity, overflow, or hot spots
Run only the commands needed for this question. Save the report with the floorplan version and analysis context.
Healthy, Suspicious & Hard-stop Results
- Healthy: Early congestion estimates compare routing demand with available capacity in coarse regions. Overflow means demand exceeds capacity on one or more routing resources.
- Hard stop: required legality or physical feasibility is missing or unexplained.
Common Mistake
The Trap: Do not hide the symptom with an arbitrary utilisation, halo, channel, blockage, pin move, or die-size change.
What The Interviewer Is Testing
” to measurable physical evidence and an owned correction.
Physical Design & Planning Handbook
Master ASIC Physical Design Planning & Floorplanning
Dive into 14 comprehensive chapters covering netlist sanity, FinFET grids, macro placement, power grids, CTS, and timing budgeting.
Offline PDF Bundle
Want all 1109 questions offline?
Get the complete 4-book PDF bundle (PnR, STA, MMMC, Low Power) with a clickable table of contents - no ads, no internet needed.
Continue practising