Under the Hood of .NET Memory Management - Simple Talk

More documents

Recommendations

Info

Acknowledgements I would like to thank my family for their patience as I spent many hours researching some arcane nuances of memory management, occasionally finding contradictions to long-held beliefs, but always learning something new. I know that it was not always easy for them. Nick Harrison About the Technical Reviewer Paul Hennessey is a freelance software developer based in Bath, UK. He is an MCPD, with a B.Sc. (1 st Class Hons.) and M.Sc. in Computer Science. He has a particular interest in the use of agile technologies and a domain-driven approach to web application development. He spent most of his twenties in a doomed but highly enjoyable bid for fame and fortune in the music business. Sadly, a lot of memories from this period are a little blurred. When he came to his senses he moved into software, and spent nine years with the leading software engineering company, Praxis, working on embedded safety-critical systems. Sadly, very few memories from this period are blurred. He now spends his time building web applications for clients including Lloyds Banking Group, South Gloucestershire Council, and the NHS. He is also an active member of the local .NET development community. x
Introduction Tackling .NET memory management is very much like wrestling smoke; you can see the shape of the thing, you know it's got an underlying cause but, no matter how hard you try, it's always just slipping through your fingers. Over the past year, I've been very involved in several .NET memory management projects, and one of the few things I can say for sure is that there is a lot of conflicting (or at any rate, nebulous) information available online. And even that's pretty thin on the ground. The .NET framework is a triumph of software engineering, a complex edifice of interlocking parts, so it's no wonder concrete information is a little hard to come by. There are a few gems out there, hidden away on MSDN, articles, and personal blogs, but structured, coherent information is a rare find. This struck us as, shall we say, an oversight. For all that the framework is very good at what it does, it is not infallible, and a deeper understanding of how it works can only improve the quality of the code written by those in the know. We'll start with the foundations: an introduction to stacks and heaps, garbage collection, boxing and unboxing, statics and passing parameters. In the next two chapters, we'll clear away some misconceptions and lay out a detailed, map of generational garbage collection, partial garbage collection, weak references – everything you need to have a solid understanding of how garbage collection really works. Chapters 4 and 5 will be practical, covering troubleshooting advice, tips, and tricks for avoiding encountering memory issues in the first place. We'll consider such conundrums as "how big is a string," fragmentation, yield, lambda, and the memory management quirks which are unique to WPF, ASP.NET, and ADO.NET, to name just a few. To really give you the guided tour, we'll finish by covering some more advanced .NET topics: parallelism, heap implementation, and the Windows memory model. 11
Page 1 and 2: .NET Handbooks Under the Hood of .N
Page 3 and 4: Copyright November 2011 ISBN 978-1-
Page 5 and 6: Workstation GC mode ...............
Page 7 and 8: Section 3: Deeper .NET ............
Page 9: I also want to thank the countless
Page 13 and 14: Section 1: Introduction to .NET Mem
Page 15 and 16: Chapter 1: Prelude The truth is, by
Page 17 and 18: Chapter 1: Prelude 7 { 8 int multip
Page 19 and 20: Chapter 1: Prelude These are primit
Page 21 and 22: Chapter 1: Prelude 1 void ValueTest
Page 23 and 24: Chapter 1: Prelude On the other han
Page 25 and 26: Chapter 1: Prelude Because paramete
Page 27 and 28: Chapter 1: Prelude 1 int i=12; 2 Ar
Page 29 and 30: Chapter 1: Prelude When an Order is
Page 31 and 32: Chapter 1: Prelude Void Mark(object
Page 33 and 34: Chapter 1: Prelude To access each m
Page 35 and 36: Chapter 1: Prelude [ThreadStatic] p
Page 37 and 38: Chapter 2: The Simple Heap Model Co
Page 39 and 40: Chapter 2: The Simple Heap Model Wh
Page 41 and 42: Chapter 2: The Simple Heap Model Fi
Page 43 and 44: Chapter 2: The Simple Heap Model th
Page 49 and 50: Chapter 2: The Simple Heap Model Ob
Page 51 and 52: Chapter 2: The Simple Heap Model ou
Page 53 and 54: Chapter 2: The Simple Heap Model Pe
Page 55 and 56: Chapter 2: The Simple Heap Model La
Page 57 and 58: Chapter 2: The Simple Heap Model Ul
Page 59 and 60: Chapter 3: A Little More Detail Now
Page 61 and 62:
Chapter 3: A Little More Detail It'
Page 63 and 64:
Chapter 3: A Little More Detail In
Page 65 and 66:
Chapter 3: A Little More Detail Con
Page 67 and 68:
Chapter 3: A Little More Detail Bac
Page 69 and 70:
Chapter 3: A Little More Detail Alt
Page 71 and 72:
Page 73 and 74:
Chapter 3: A Little More Detail Wea
Page 75 and 76:
Chapter 3: A Little More Detail …
Page 77 and 78:
Chapter 3: A Little More Detail GC
Page 79 and 80:
Page 81 and 82:
What's Coming Next In this next sec
Page 83 and 84:
• Use a struct to represent any i
Page 86 and 87:
Chapter 4: Common Memory Problems T
Page 88 and 89:
Chapter 4: Common Memory Problems V
Page 90 and 91:
Chapter 4: Common Memory Problems c
Page 92 and 93:
Chapter 4: Common Memory Problems i
Page 94 and 95:
Chapter 4: Common Memory Problems u
Page 96 and 97:
Page 98 and 99:
Chapter 4: Common Memory Problems i
Page 100 and 101:
Chapter 4: Common Memory Problems S
Page 102 and 103:
Chapter 4: Common Memory Problems p
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Chapter 4: Common Memory Problems s
Page 110 and 111:
Chapter 4: Common Memory Problems Y
Page 112 and 113:
Chapter 4: Common Memory Problems v
Page 114 and 115:
Chapter 4: Common Memory Problems {
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Chapter 4: Common Memory Problems [
Page 122 and 123:
Page 124 and 125:
Chapter 4: Common Memory Problems D
Page 126 and 127:
Page 128 and 129:
Chapter 4: Common Memory Problems C
Page 130 and 131:
Chapter 4: Common Memory Problems W
Page 132 and 133:
Page 134 and 135:
Chapter 4: Common Memory Problems [
Page 136 and 137:
Chapter 4: Common Memory Problems A
Page 138 and 139:
Page 140 and 141:
Chapter 4: Common Memory Problems U
Page 142 and 143:
Page 144 and 145:
Chapter 4: Common Memory Problems K
Page 146 and 147:
Chapter 5: Application-Specific Pro
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Section 3: Deeper .NET
Page 180 and 181:
Chapter 6: A Few More Advanced Topi
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Chapter 7: The Windows Memory Model
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
.NET and SQL Server Tools from Red
Page 216 and 217:
.NET Reflector ® Decompile, browse
Page 218 and 219:
SQL Prompt Pro Write, edit, and exp
Page 220 and 221:
SQL Monitor SQL Server performance
Page 222 and 223:
SQL Toolbelt The essential SQL Serv
Page 224:
Brad's Sure Guide to SQL Server Mai
show all

Under the Hood of .NET Memory Management - Simple Talk

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?