.NET news » Performance

This article is dedicated to the observable property design pattern, a very nice pattern used in the Microsoft .NET Framework, a possible memory leak problem with it, and gives a couple of ways to solve it.

Provides code and techniques to enable developers to optimize serialization of DataSets/DataTables.

Uncovering and correcting memory issues in managed applications can be difficult. Memory issues manifest themselves in different ways. For example, you may observe your application's memory usage growing unboundedly, eventually resulting in an Out Of Memory (OOM) exception. (Your application may even throw out-of-memory exceptions when there is plenty of physical memory available.) But any one of the following may indicate a possible memory issue:

• An OutOfMemoryException is thrown.
• The process is using too much memory for no obvious reason that you can determine.
• It appears that garbage collection is not cleaning up objects fast enough.
• The managed heap is overly fragmented.
• The application is excessively using the CPU.

This column discusses the investigation process and shows you how to collect the data you need to determine what types of memory issues you are dealing with in your applications. This column does not cover how to actually fix problems you find, but it does give some good insights as to where to start.

Appending to an XML file can be tricky with large files in terms of speed and memory usage. This article covers the options available in .NET.

A simple and fast random number generator that can be substituted in place of System.Random, with extra methods and fast re-initialization.

ASP.NET Applications speed optimizations regarding to use of page and server controls, web application settings and best coding practices

Describes how to create your own custom profiler for any managed application

The AltSerializer is a replacement for the binary serializer built in to .NET.

Ever wanted something faster than SetPixel? Well you've found it.

This tool analyses the IL of a list of assemblies, looking for types, methods, and fields that are not used by another list of assemblies. This lets you see if you have unused legacy code lying around that should be cleaned up.