What Every Programmer Should Know About Memory

N/A

# link_19jkogybix4.pdf ## Metadata - PDFFormatVersion=1.5 - IsLinearized=false - IsAcroFormPresent=false - IsXFAPresent=false - IsCollectionPresent=false - IsSignaturesPresent=false - CreationDate=D:20060619205600-08'00' - Author=Ulrich Drepper Red Hat, Inc. drepper@redhat.com - Title=What Every Programmer Should Know About Memory - Creator=LaTeX with hyperref package - Producer=pdfTeX-1.40.3 - Keywords=Linux, Programming, Memory, Cache, Performance, Hardware - ModDate=D:20071121175207-08'00' - Trapped=False - Custom.PTEX.Fullbanner=This is pdfTeX, Version 3.141592-1.40.3-2.2 (Web2C 7.5.6) kpa

saved by

• Varun Shenoy
• Julian Quevedo
• Ayodeji Adesegun
• Benedict Neo
• Gabriel Bartmanovicz

related reading

• What every programmer should know about memory, Part 1 [LWN.net]lwn.net
• A Close Look at SRAM for Inference in the Age of HBM Supremacyviksnewsletter.com
• Making Deep Learning go Brrrr From First Principleshorace.io
• Memory-Limited Layers User's Guide - NVIDIA Docsdocs.nvidia.com
• theartofhpc.com/istc/sequential.html#ThevonNeumannarchitecturetheartofhpc.com
• DRAM、NAND Flash 最近貴到炸，你還搞不懂記憶體的差異嗎？ - 寫點科普 Lynnkopu.chat
• Memory access is O(N^[1/3])vitalik.eth.limo
• Memory Mania: How a Once-in-Four-Decades Shortage Is Fueling a Memory Boomnewsletter.semianalysis.com
• Memory location matters for performancepythonspeed.com
• Infographics: Operation Costs in CPU Clock Cycles - 6IT6it.dev
• Non-volatile random-access memory - Wikipediaen.wikipedia.org
• INTELLIGENCEstacks.stanford.edu