DotNetKicks.com - Stories tagged with Optimization

Do modern compilers optimize the x * 2 operation to x << 1?

Wed, 18 Feb 2009 09:05:29 GMT

I was wondering wether the C++ compiler inside Visual Studio 2008 was optimizing it the way it would logically be. So I asked the question on Stackoverflow. It was among my first questions and was to see how the community would answer (yeah I'm lazy). I was promptly answered by Rob Walker. He showed me what the compiler outputted.

How the Garbage Collector works - Part 2

Sat, 03 May 2008 22:46:56 GMT

Now let's go deeper to understand how the Garbage Collector (GC) is actually collecting the dead objects and how this may affect the performance.

How the Garbage Collector works - Part 1

Sat, 03 May 2008 19:37:35 GMT

The Garbage Collector (GC) can be considered the heart of the .NET Framework. It manages the allocation and release of memory for any .NET application. In order to create good .NET applications, we must know how the Garbage Collector (GC) works.

10 Tips to improve your LINQ TO SQL Application Performance

Fri, 02 May 2008 22:46:03 GMT

Sidar gives performance tips on developing linq 2 sql

Boosting performance on aspx pages

Mon, 31 Mar 2008 23:00:34 GMT

Most of internet tutorials tells you to use Page Load event to bind your data to controls. What's happening when you have to rebind controls again because your data source is changed due to some event where you have to re bind controls.

Things you MUST dispose

Wed, 02 Apr 2008 16:46:02 GMT

When the .NET Framework instantiates an object, it allocates memory for that object on the managed heap. The object remains on the heap until it's no longer referenced by any active code, at which point the memory it's using is reclamed by the Garbage Collector (GC). Before the GC deallocates the memory, the framework calls the object's Finalize() method, but developers are responsible for calling the Dispose() method.

How to: Optimize the memory usage with strings

Mon, 31 Mar 2008 18:16:03 GMT

System.String type is used in any .NET application. We have strings as: names, addresses, descriptions, error messages, warnings or even application settings. Each application has to create, compare or format string data. Considering the immutability and the fact that any object can be converted to a string, all the available memory can be swallowed by a huge amount of unwanted string duplicates or unclaimed string objects. Now let's see how a string object should be handled to preserve memory.

How to: Optimize the strings' comparison

Sat, 29 Mar 2008 17:15:40 GMT

Due to my web research I found some useful tips about how to compare two strings making full use of performance in .NET Framework.

Optimization: Your worst enemy

Sat, 18 Aug 2007 19:01:02 GMT

Good article on why optimization can be bad, and what you can do about it.

SQL Optimization Tips

Tue, 14 Aug 2007 17:31:02 GMT

Tips and Tricks which should be used while dealing with SQL

Optimized access to Bitmaps

Wed, 23 May 2007 16:46:01 GMT

How to read and elaborate sequence of bitmaps without using .NET functions, saving tons of processor cycles.

Optimize it!

Tue, 13 Feb 2007 03:16:01 GMT

How to achive good performance