Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Reading Path
  • STA Glossary
  • STA Metrics Reference
  • STA Mastery Cheatsheet
  • Timing Paths and Checks16
  • Constraints & SDC Fundamentals20
  • Delay Graph & Path Analysis16
    • Graph Traversal & Slack
    • Cell vs Net Delay Budgets
      • Where the Delay Goes
      • Sizing and Delay Sensitivity
      • Wire Load and Routed Parasitics
      • Budgeting a Path
    • Path Group Prioritization
    • Report Timing Deep Read
  • Beyond Setup and Hold16
  • Multi-Corner Multi-Mode Signoff16
  • OCV, AOCV, POCV and Variation16
  • Crosstalk and Noise16
  • ECO and Closure16
  • STA Debug Playbook16
  • STA Interview Prep26
  • Capstone Timing Signoff Lab4
Loading lesson

‹Delay Graph & Path Analysis
  1. Topics
  2. Static Timing Analysis
  3. Delay Graph & Path Analysis
  4. Cell vs Net Delay Budgets

Part 3 · Delay Graph and Path Analysis · All levels

Cell vs Net Delay Budgets

Where the delay on a path actually goes, how sizing changes it, how pre-route estimates differ from routed parasitics, and how to budget a path.

  • 4topics
  • 4lessons

A violating path always has a dominant cause, and fixing it starts by knowing the split between cell delay and wire delay. This topic breaks a path down, shows how sizing trades delay against load, explains why pre-route numbers differ from routed ones, and teaches budgeting a path before implementation.

Lesson

After it you can...

Where the Delay Goes

Split a path into clock-to-Q, cells and wires.

Sizing and Delay Sensitivity

Predict what upsizing does, including to the stage before.

Wire Load and Routed Parasitics

Explain why estimates and routed numbers differ.

Budgeting a Path

Assign a delay budget to each stage and check the sum.

The models behind these numbers are in Delay Models.

Check yourself A path fails by 0.2 ns and 60% of its delay is wire. What does that change about the fix?

Resizing cells helps little; buffering, layer changes, shorter routes or placement changes address the dominant wire delay.

Interview

Always start a fix discussion by asking for the split: cell versus wire, and which stage is largest.

PreviousNext: Where the Delay Goes

Up next

Up nextWhere the Delay Goes

Sign in to save progress

Practice this lessonReport an error

See also

  • Graph Traversal & Slack
  • Path Group Prioritization
  • Report Timing Deep Read