Large Object Heap Compaction, when is it good?

by

Allocations >= 85 KB go onto the LOH. Compacting the LOH is not bad — it’s just that LOH fragmentation isn’t something the great majority of apps need to worry about, so for them it’s not worth the expense of compacting.

Fragmentation occurs when you allocate several large objects and they all get taken from the same page of address space, then let some of those objects get collected. The remaining free space in that page might be unusable because it is too small, or even simply “forgotten” in the sense that the allocator won’t ever reconsider using it again.

Eventually there are fewer and fewer clean pages to use, so the allocator will start to slow down as it forcibly moves objects or even start throwing OutOfMemory exceptions. Compaction moves those objects to new pages, reclaiming that free space.

Does your app have this object usage pattern? Most don’t. And on 64-bit platforms, you might not even notice it as there’s quite a bit more address space to fragment before it becomes a huge issue.

More Related Contents:

  1. What is the purpose of “return await” in C#?
  2. How do I make calls to a REST API using C#?
  3. Awaiting multiple Tasks with different results
  4. Setting Objects to Null/Nothing after use in .NET
  5. Does using “new” on a struct allocate it on the heap or stack?
  6. Attempted to read or write protected memory. This is often an indication that other memory is corrupt
  7. Implementing IDisposable correctly
  8. What strategies and tools are useful for finding memory leaks in .NET?
  9. Large Object Heap Fragmentation
  10. Is there any benefit of using an Object Initializer?
  11. There is no argument given that corresponds to the required formal parameter – .NET Error
  12. .NET Memory issues loading ~40 images, memory not reclaimed, potentially due to LOH fragmentation
  13. Format A TimeSpan With Years
  14. How does Task become an int?
  15. Is it possible to run a .NET 4.5 app on XP?
  16. Await operator can only be used within an Async method [duplicate]
  17. C# memory address and variable
  18. Creating Directories in a ZipArchive C# .Net 4.5
  19. High memory consumption with Enumerable.Range?
  20. Create zip file from byte[]
  21. Initial capacity of collection types, e.g. Dictionary, List
  22. How is memory allocated for a static variable?
  23. Thread parameters being changed
  24. What causes memory fragmentation in .NET
  25. How do I get .NET to garbage collect aggressively?
  26. .NET 4.5 Bug in UserPrincipal.FindByIdentity (System.DirectoryServices.AccountManagement)
  27. Memory limitations in a 64-bit .Net application?
  28. When exactly does .NET Monitor go to kernel-mode?
  29. Decompressing password-protected ZIP files with .NET 4.5
  30. Run async method 8 times in parallel

Leave a Comment