Ac Memory Layout And Caches

How a program's memory behaves on real hardware: cache lines and what sharing one costs, the memory hierarchy's latency ladder, false sharing and padding as a fix, aligned access and unaligned penalties, prefetching and the access pattern that makes it useless, page faults and the major-minor split, NUMA and the locality that decides remote memory costs, and the written layout record. It explains how data placement performs and how to observe it; it never recommends a processor and never promises a speedup. Use when asking "cache line", "false sharing", "memory alignment", "prefetch", "page fault", "NUMA", "memory latency", "cache miss", "why is iteration order so much faster", "padded structure", "locality of reference". Not for profiling methodology in general (ac-performance), not for page allocation inside a database engine (ac-query-and-index-design), not for OS process memory limits (ac-resource-exhaustion-diagnosis).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit 0f7a9c1cd9

Frequently asked questions

npx get-skill add jiayaoqijia/ac-memory-layout-and-caches