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

  • Architecture Metrics Reference
  • Workload Taxonomy for Architects
  • Architecture Glossary
  • Computer Architecture Cheatsheet
  • Pipeline Fundamentals14
  • Memory Hierarchy15
  • NoC and Interconnect Architecture6
  • Coherency and Memory Ordering9
  • Performance Analysis9
  • Accelerator Architectures6
  • SoC Architecture Tradeoffs9
  • Architecture Interview Prep14
Loading lesson

‹Computer Architecture
  1. Topics
  2. Computer Architecture
  3. Computer Architecture Cheatsheet

Computer Architecture · All levels

Computer Architecture Cheatsheet

Bounds, formulas, and interview one-liners for architecture debug, corrected and cross-checked.

On this page

    One page for debug order, bounds, and formulas. Every formula matches the metrics reference.

    Bound taxonomy

    Frontend bound: I-cache miss, branch mispredict, or fetch width starves decode. Backend bound: execution ports, scheduler depth, or long-latency ops stall retire. Memory bound: LSU queue depth, cache miss, or MSHR limits cap MLP.

    Virtual channels isolate traffic classes; VC-partitioned routing with an acyclic channel dependency graph breaks routing deadlock. Protocol-level deadlock still needs separate request and response classes.

    Formulas

    CPI equals 1 over IPC. AMAT equals hit time plus miss rate times miss penalty. Delivered bandwidth is demand rate capped by link and DRAM realities. Roofline says performance stays under the lower of peak compute and bandwidth times intensity. Amdahl caps speedup by the unimproved fraction.

    Strong answers, weak answers

    Strong: on workload X, MPKI rose from 8 to 14, mostly L2 conflict misses after the layout change. Weak: the cache is slow.

    Strong: p99 latency spikes when DMA and coherent reads share a virtual channel. Weak: the NoC is congested.

    Strong: the roofline shows kernel B is memory bound, so wider SIMD is not the first fix. Weak: we need more cores.

    Related topics

    • Course Hub

    • Metrics Reference

    • Glossary

    • Interview Method and Worked Scenarios

    Previous

    4 / 86

    Next: Pipeline Fundamentals

    Up next

    Up nextPipeline Fundamentals

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Architecture Metrics Reference
    • Workload Taxonomy for Architects
    • Memory Hierarchy