Reference Types Performance MS Peeps please sound off!

  • Thread starter Thread starter Quizical
  • Start date Start date
Q

Quizical

First, is null considered a Value Type or a Reference Type.

I have a question about performance and memory. Does the performance
change or the amount of memory that is consumed when you have a
difference in flow control statements as follows:

//Arbitrary Reference Type
Mailmessage mm = new Mailmessage();
//A
if (null != mm)
{
Console.WriteLine(mm.ToString());
}

Or

//B
if (mm != null)
{
Console.WriteLine(mm.ToString());
}

I have been told that A performs better since the CLR does not have to
make a copy of the value null, I think it doesn't matter since both
values must be checked regardless. (I also think this reads like crap)

Please Help!
 
Quizical said:
First, is null considered a Value Type or a Reference Type.
Click to expand...

null is a reference.
I have a question about performance and memory. Does the performance
change or the amount of memory that is consumed when you have a
difference in flow control statements as follows:

//Arbitrary Reference Type
Mailmessage mm = new Mailmessage();
//A
if (null != mm)
{
Console.WriteLine(mm.ToString());
}

Or

//B
if (mm != null)
{
Console.WriteLine(mm.ToString());
}

I have been told that A performs better since the CLR does not have to
make a copy of the value null, I think it doesn't matter since both
values must be checked regardless. (I also think this reads like crap)
Click to expand...

Neither version uses null - the test compiles to

ldloc.0 // Put the value of mm on the stack
brfalse.s [whatever] // Skip the block if the topmost stack value is 0

Given that the IL is the same in both cases, the JITted code should be
the same too.

Oh, and I agree that B reads better too - and that, to me, would be far
more important than any tiny performance gains which could be had if A
were in fact slightly different. Micro-optimisations like this attempts
to achieve should not be used unless that section of code is *proven*
to be a bottleneck.
 
Back
Top