Performance surprise with “as” and nullable types

by

Clearly the machine code the JIT compiler can generate for the first case is much more efficient. One rule that really helps there is that an object can only be unboxed to a variable that has the same type as the boxed value. That allows the JIT compiler to generate very efficient code, no value conversions have to be considered.

The is operator test is easy, just check if the object isn’t null and is of the expected type, takes but a few machine code instructions. The cast is also easy, the JIT compiler knows the location of the value bits in the object and uses them directly. No copying or conversion occurs, all machine code is inline and takes but about a dozen instructions. This needed to be really efficient back in .NET 1.0 when boxing was common.

Casting to int? takes a lot more work. The value representation of the boxed integer is not compatible with the memory layout of Nullable<int>. A conversion is required and the code is tricky due to possible boxed enum types. The JIT compiler generates a call to a CLR helper function named JIT_Unbox_Nullable to get the job done. This is a general purpose function for any value type, lots of code there to check types. And the value is copied. Hard to estimate the cost since this code is locked up inside mscorwks.dll, but hundreds of machine code instructions is likely.

The Linq OfType() extension method also uses the is operator and the cast. This is however a cast to a generic type. The JIT compiler generates a call to a helper function, JIT_Unbox() that can perform a cast to an arbitrary value type. I don’t have a great explanation why it is as slow as the cast to Nullable<int>, given that less work ought to be necessary. I suspect that ngen.exe might cause trouble here.

More Related Contents:

  1. C# ‘is’ operator performance
  2. Float vs Double Performance
  3. Boxing / Unboxing Nullable Types – Why this implementation?
  4. Is a LINQ statement faster than a ‘foreach’ loop?
  5. How do ValueTypes derive from Object (ReferenceType) and still be ValueTypes?
  6. Handling warning for possible multiple enumeration of IEnumerable
  7. Prevent .NET Garbage collection for short period of time
  8. Nullable type is not a nullable type?
  9. Is there a performance impact when calling ToList()?
  10. C# elegant way to check if a property’s property is null
  11. Performance Tests of Serializations used by WCF Bindings
  12. Performance of calling delegates vs methods
  13. HttpWebRequest is extremely slow!
  14. c# – Volatile keyword usage vs lock
  15. Efficient Cartesian Product algorithm
  16. sizeof(int) on x64?
  17. Static vs. non-static method
  18. Is there any performance difference between ++i and i++ in C#?
  19. C# quickest way to shift array
  20. System.Net.WebClient unreasonably slow
  21. Linq query with nullable sum
  22. Where in memory are nullable types stored?
  23. How much faster is C++ than C#?
  24. Why does struct alignment depend on whether a field type is primitive or user-defined?
  25. How do I measure how long a function is running?
  26. Why only literal strings saved in the intern pool by default?
  27. Type result with conditional operator in C#
  28. What is the default value of the nullable type “int?” (including question mark)?
  29. How to read last “n” lines of log file [duplicate]
  30. variable scope in statement blocks

Leave a Comment