Book Image

High-Performance Programming in C# and .NET

By : Jason Alls
Book Image

High-Performance Programming in C# and .NET

By: Jason Alls

Overview of this book

Writing high-performance code while building an application is crucial, and over the years, Microsoft has focused on delivering various performance-related improvements within the .NET ecosystem. This book will help you understand the aspects involved in designing responsive, resilient, and high-performance applications with the new version of C# and .NET. You will start by understanding the foundation of high-performance code and the latest performance-related improvements in C# 10.0 and .NET 6. Next, you’ll learn how to use tracing and diagnostics to track down performance issues and the cause of memory leaks. The chapters that follow then show you how to enhance the performance of your networked applications and various ways to improve directory tasks, file tasks, and more. Later, you’ll go on to improve data querying performance and write responsive user interfaces. You’ll also discover how you can use cloud providers such as Microsoft Azure to build scalable distributed solutions. Finally, you’ll explore various ways to process code synchronously, asynchronously, and in parallel to reduce the time it takes to process a series of tasks. By the end of this C# programming book, you’ll have the confidence you need to build highly resilient, high-performance applications that meet your customer's demands.
Table of Contents (22 chapters)
1
Part 1: High-Performance Code Foundation
7
Part 2: Writing High-Performance Code
16
Part 3: Threading and Concurrency

Chapter 4, Memory Management

  1. Three: generation 0, generation 1, and generation 2.
  2. Objects less than 80,000 bytes are placed on the SOH.
  3. Objects 80,000 bytes or more are placed on the LOH.
  4. A strong reference is a reference that does not get garbage-collected.
  5. A weak reference is a reference that does get garbage-collected.
  6. Implement the IDisposable pattern.
  7. Unsubscribe event listeners when they are no longer used. Dispose of event publishers or set them to null when they are no longer used.
  8. Marshal.ReleaseComObject(object).
  9. Make sure that any allocated memory is deallocated. Use the IDisposable pattern to ensure that memory is cleaned up when the object is disposed of.