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
  • Beyond Setup and Hold16
  • Multi-Corner Multi-Mode Signoff16
  • OCV, AOCV, POCV and Variation16
    • OCV, AOCV and POCV Mechanisms
    • Derate Policy and Approval
    • Path Depth Sensitivity
      • Depth Versus Variation
      • Short Paths Versus Long
      • Clock Path Variation
      • Worked Comparison
    • Variation Signoff Dashboard
  • Crosstalk and Noise16
  • ECO and Closure16
  • STA Debug Playbook16
  • STA Interview Prep26
  • Capstone Timing Signoff Lab4
Loading lesson

‹Path Depth Sensitivity
  1. Topics
  2. Static Timing Analysis
  3. OCV, AOCV, POCV and Variation
  4. Path Depth Sensitivity
  5. Short Paths Versus Long

Part 6 · OCV, AOCV, POCV and Variation · All levels

Short Paths Versus Long

Hold paths are short and carry a large relative derate; setup paths are deep and carry a smaller one; a flat derate over-charges the deep ones.

On this page

    Why it matters

    Hold fixes are usually found on very short paths, where relative variation is greatest. Setup problems are usually on long paths, where a flat derate is most wasteful. Putting both on one scale shows where each method matters.

    Worked example

    example.py
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    import math
    def spread(n, k=3.0, s=0.05):
        return k * s / math.sqrt(n)                    # relative derate from depth (same model as the depth lesson)
    # Hold: 2-stage path of 0.20 ns; hold requirement including skew 0.10 ns.
    hold_path, hold_req, flat_early = 0.20, 0.10, 0.85
    slack_nominal = hold_path - hold_req
    slack_flat = hold_path * flat_early - hold_req
    slack_depth = hold_path * (1 - spread(2)) - hold_req
    assert round(slack_nominal, 3) == 0.10 and round(slack_flat, 3) == 0.07 and round(slack_depth, 4) == 0.0788
    # Setup: 20-stage path of 2.00 ns.
    setup_path = 2.00
    cost_flat = setup_path * 0.15
    cost_depth = setup_path * spread(20)
    assert round(cost_flat, 3) == 0.300 and round(cost_depth, 3) == 0.067
    assert round(cost_flat - cost_depth, 3) == 0.233
    print("PASS: hold slack nominal/flat/depth", round(slack_nominal, 3), round(slack_flat, 3), round(slack_depth, 4), "; setup cost flat/depth", round(cost_flat, 3), round(cost_depth, 3))

    Path

    Method

    Effect

    Hold, 2 stages, 0.20 ns

    Nominal

    Slack 0.100 ns

    Hold, 2 stages, 0.20 ns

    Flat early 0.85

    Slack 0.070 ns

    Hold, 2 stages, 0.20 ns

    Depth-based (0.894)

    Slack 0.079 ns

    Setup, 20 stages, 2.00 ns

    Flat late 1.15

    Costs 0.300 ns

    Setup, 20 stages, 2.00 ns

    Depth-based (1.034)

    Costs 0.067 ns

    On the short hold path the derate is large in relative terms (10.6% for two stages) but small in absolute terms because the path is short: 0.021 ns against 0.030 ns for flat. On the deep setup path the same two methods differ by 0.233 ns, which is a large part of a typical margin budget. Depth-based analysis therefore matters most for setup closure on long paths, while hold closure is dominated by how small the absolute slack already is.

    What the review looks for

    • Hold analysis uses the early derate on the launch path and the late derate on the capture clock; setup the reverse.

    • Short paths are reviewed for absolute slack, because a small relative derate can still consume a small margin.

    • Setup paths with large derate cost are the first to benefit from a method change; show the saving before proposing one.

    Common pitfall

    Treating hold derate as negligible because the path is short. The absolute change is small, but hold margins are small too, and the clock paths carry variation of their own.

    Interview

    Explain that relative derate is largest for short paths, absolute cost largest for long ones.

    Check yourself Which path in the example benefits more from depth-based analysis in absolute terms?

    The 20-stage setup path, which gains 0.233 ns; the 2-stage hold path gains only about 0.009 ns.

    Related topics

    • Depth Versus Variation

    • Next: Clock Path Variation

    Previous

    99 / 183

    Next: Clock Path Variation

    Up next

    Up nextClock Path Variation

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Worked Comparison