Memory hierarchy
The memory hierarchy layers fast small caches over slower large memory, so most accesses hit the fast layers.
At a glance
Key signals
0% cross fields · reaches 1 more
- Computer Architecture
- Computer Science
- Computer Engineering
- Explanation
- Examples
- Misconception
- Sourced relations
- Attribution
Dependencies
What this concept builds on and what it makes possible — derived from the atlas’s dependency, causal and structural relations, not from every related edge.
Foundations · builds on
Memory hierarchydepends onSystem busEstablished
Memory hierarchy depends on System bus.
Enables · leads to
Memory hierarchyenablesCentral processing unitEstablished
Open Central processing unit →
The memory hierarchy keeps the CPU fed.
Mechanism: Small fast caches hold recently used data near the CPU, so it rarely waits on slow main memory.
System context
Memory hierarchyis part ofVon Neumann ArchitectureEstablished
Open Von Neumann Architecture →
Memory hierarchy is a part of Von Neumann Architecture.
Cache Memoryis part ofMemory hierarchyEstablished
Cache memory is a part of Memory hierarchy.
Virtual memoryis part ofMemory hierarchyEstablished
Virtual Memory is a part of Memory hierarchy.
Structural role & consequence
Interpreted from the current atlas graph — what the connections mean, not just how many there are.
Directly enables 1 concept; following enables/causes relations, 1 concept is downstream across 1 discipline.
structural · Follows only enables/causes dependency edges — not general relatedness.
Currently dark in the atlas: no key date stored · 6 of 6 of its relations lack claim-level evidence.
atlas representation · Describes the current Thinking OS representation, not the state of the world.
Builds on 1 foundation (requires / depends-on / derived-from / emerges-from).
structural · Structural graph analysis — not a claim of importance, causation or history.
Structural neighbourhood: 6 → 17 → 35 concepts reachable within 3 hops.
structural · Structural reach — being reachable is not the same as being understood.
cross-field
6 within-field, 0 cross-field
Strengths & constraints
Constraints
- Evidence coverage currently thin in the atlas — few of its relationships carry claim-level evidence. atlas representation
- No dated history stored — the atlas records no key date for this concept. atlas representation
Conditions
- Its dependency reading rests on 1 foundation relation. structural
- Read structurally — most of its relationships carry no external evidence yet, so claims here are graph-derived. structural
Dependency radial
What this concept builds on (left) and what it makes possible (right) — derived from dependency and causal relations.
Seen through each discipline
How this concept sits in each of its fields — derived from its real connections in the graph, not asserted.
Through this lens it connects to Cache Memory, Virtual memory, Pipeline and Von Neumann Architecture.
Through this lens it connects to Central processing unit, Virtual memory and Pipeline.
Through this lens it connects to Cache Memory and System bus.
Related ideas to explore
Concepts that look related but are not yet connected here — candidates for a connection to reason about, not established links.
- Connects 6 other ideas across 3 disciplines.
- A local hub: unusually many ideas converge here.
- Most of its connections are of the “Kind & structure” kind.
Derived from the graph’s real structure — observations, not a score.
Sources
- A Unified Compressed Memory Hierarchy verified
- Initial Experiences with Dreamy Memory and the RAMpage Memory Hierarchy (2004) verified
- Memory Hierarchy (2012) verified
- Replacing Different Levels of the Memory Hierarchy with NVMs (2013) verified
- Exploitation of the Memory Hierarchy in Relational DBMSs (2003) verified