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
    • Caches
      • Address Decode and the Access Path
      • Associativity and the Three Cs
      • AMAT, MPKI and Memory-Level Parallelism
      • Replacement and Thrashing
      • Write Policies and Coherence Hooks
      • Sizing a Level and Triaging Misses
    • Memory Bandwidth and Latency
    • Virtual Memory and the TLB
  • NoC and Interconnect Architecture6
  • Coherency and Memory Ordering9
  • Performance Analysis9
  • Accelerator Architectures6
  • SoC Architecture Tradeoffs9
  • Architecture Interview Prep14
Loading lesson

‹Memory Hierarchy
  1. Topics
  2. Computer Architecture
  3. Memory Hierarchy
  4. Caches

Computer Architecture · All levels

Caches

How sets, ways and address decode set hit latency, miss rate and cache area.

  • 6topics
  • 6lessons

A cache trades hit latency against miss rate under area and power caps. Every lesson below derives its numbers from stated formulas and small runnable models.

Organization

Compare cost

Miss behavior

When it fits

Direct-mapped

One tag compare, fastest hit

Conflict misses on any alias

Tiny structures or historical baselines

Set-associative

One compare per way, slower hit

Fewer conflict misses as ways grow

Most L1, L2 and LLC levels

Fully associative

A compare per line, slowest and hottest

No conflict misses, only capacity and compulsory

Small buffers such as TLBs

Victim cache

One small fully associative side buffer

Catches conflict evictions before they leave

Direct-mapped or low-way L1 designs

Lesson

What it covers

Address decode and the access path

Index, tag and offset split, and the hit and miss path.

Associativity and the three Cs

Ways, miss classes, and measured conflict misses.

AMAT, MPKI and memory-level parallelism

Average access time, correct MPKI use, and overlap.

Replacement and thrashing

Victim choice, Belady bound, and insertion fixes.

Write policies and coherence hooks

Write hit and miss options, traffic, and directory costs.

Sizing a level and triaging misses

A scored trade study and the MPKI split method.

Check yourself A larger cache raises the hit rate but slows the clock on hits. Which single metric decides whether it helped?

Average memory access time. It combines hit latency with miss rate times miss penalty, so it prices both sides of the trade.

Interview

State the one-sentence answer first: organization sets hit latency, miss rate and parallelism together. Then price any proposal with AMAT, MPKI split by cause, and perf per watt.

PreviousNext: Address Decode and the Access Path

Up next

Up nextAddress Decode and the Access Path

Sign in to save progress

Practice this lessonReport an error

See also

  • Memory Bandwidth and Latency
  • Virtual Memory and the TLB