5,699,997 members and growing! (14,908 online)
Email Password   helpLost your password?
Languages » C# » General     Advanced

Fast Dynamic Property/Field Accessors

By Stephen Erisman

Fast run-time access to Property/Field values using the new (.NET 2.0) DynamicMethod class, and a very small amount of emitted IL code.
C#, Windows, .NET, Visual Studio, Architect, Dev

Posted: 23 Jun 2006
Updated: 4 Jul 2006
Views: 50,629
Bookmarked: 94 times
Announcements
Loading...



Search    
Advanced Search
Sitemap
24 votes for this Article.
Popularity: 6.63 Rating: 4.80 out of 5
0 votes, 0.0%
1
0 votes, 0.0%
2
1 vote, 4.2%
3
2 votes, 8.3%
4
21 votes, 87.5%
5

Introduction

Quite often, I run across the need to dynamically retrieve the value of an object's property (or field), where the actual member might not be known until run-time.

Some examples of where one might use this are:

  • Comparer for sorting an array/list/collection
  • Class to filter a collection based on member values
  • Class to serialize/deserialize a list of objects (faster than BinaryFormatter)

Background

In the past, I have made use of run-time reflection to: find a property's PropertyInfo or a field's FieldInfo, and Invoke the GetValue method of the PropertyInfo or FieldInfo on an object to retrieve the value.

PropertyInfo pi = typeof(Widget).GetProperty("ID");
Int32 id = (Int32) pi.GetValue(widget, null);

This works fine if you only have to retrieve the member's value for a single object; but once you have to get the value in a loop, it performs very slow.

The New Method (.NET 2.0)

I got to thinking, why not generate (at run-time) the same IL code that the compiler generates at compile time, and use that to call the property's get accessor or retrieve the field's value?

In previous versions of .NET (1.0 and 1.1), there is a pretty big overhead to generating IL code. This is because using the System.Reflection.Emit namespace requires an out-of-process call to csc.exe to actually generate the IL Code.

Thankfully, .NET 2.0 provides us with a new DynamicMethod class, that is a much more light-weight method of generating IL code.

Using this new DynamicMethod class, it is easy to produce a fast method for dynamically retrieving member values.

Usage

TypeUtility<Widget>.MemberGetDelegate<Int32>
GetID = TypeUtility<Widget>.GetMemberGetDelegate<Int32>("ID");
Int32 id = GetID(widget);

The Code

public class TypeUtility<ObjectType>
{
    public delegate MemberType 
           MemberGetDelegate<MemberType>(ObjectType obj);

    public static MemberGetDelegate<MemberType>
        GetMemberGetDelegate<MemberType>(string memberName)
    {
        Type objectType = typeof(ObjectType);
    
        PropertyInfo pi = objectType.GetProperty(memberName);
        FieldInfo fi = objectType.GetField(memberName);
        if (pi != null)
        {
            // Member is a Property...


            MethodInfo mi = pi.GetGetMethod();
            if (mi != null)
            {
                // NOTE:  As reader J. Dunlap pointed out...

                //  Calling a property's get accessor is faster/cleaner using

                //  Delegate.CreateDelegate rather than Reflection.Emit 

                return (MemberGetDelegate<MemberType>)
                    Delegate.CreateDelegate(typeof(
                          MemberGetDelegate<MemberType>), mi);
            }
            else
                throw new Exception( String.Format(
                    "Property: '{0}' of Type: '{1}' does" + 
                    " not have a Public Get accessor",
                    memberName, objectType.Name ) );
        }
        else if (fi != null)
        {
            // Member is a Field...

    
            DynamicMethod dm = new DynamicMethod("Get" + memberName,
                typeof(MemberType), new Type[] { objectType }, objectType);
            ILGenerator il = dm.GetILGenerator();
            // Load the instance of the object (argument 0) onto the stack

            il.Emit(OpCodes.Ldarg_0);
            // Load the value of the object's field (fi) onto the stack

            il.Emit(OpCodes.Ldfld, fi);
            // return the value on the top of the stack

            il.Emit(OpCodes.Ret);

            return (MemberGetDelegate<MemberType>)
                dm.CreateDelegate(typeof(MemberGetDelegate<MemberType>));
        }
        else
            throw new Exception( String.Format(
                "Member: '{0}' is not a Public Property or Field of Type: '{1}'",
                memberName, objectType.Name ));
    }
}

Tweaking Performance - Caching the Generated Code

There is a small amount of build up time that occurs during each call to GetMemberGetDelegate. This is due to having to generate the IL code and create a delegate. If possible, the generated delegate should be kept around for future use. Below is the code that can be used for that purpose.

public class TypeUtility<ObjectType>
{
    private static Dictionary<string,Delegate>
    _memberGetDelegates = new Dictionary<string,Delegate>();

    public static MemberGetDelegate<MemberType> 
        GetCachedMemberGetDelegate<MemberType>(string memberName)
    {
        if ( _memberGetDelegates.ContainsKey(memberName) )
            return (MemberGetDelegate<MemberType>) 
                   _memberGetDelegates[memberName];

        MemberGetDelegate<MemberType> returnValue = 
             GetMemberGetDelegate<MemberType>( memberName );
        lock ( _memberGetDelegates )
        {
            _memberGetDelegates[memberName] = returnValue;
        }
        return returnValue;
    }
}

Performance Test Results

Performance Test Screen Shot

Based on my performance tests, using the dynamically generated code is 30x-50x faster than using normal reflection. It is still only about half as fast as using compiled code, which I imagine is due to the number of method calls. With compiled code, there is only one method call: the property's get accessor. When using the run-time generated code, you end up making two method calls: first to the generated code, and second to the property's get accessor. Depending on your exact usage, you may be able to optimize further and get back to one method call.

An Example Using This Concept

I mentioned earlier that one example of where this concept could come in handy is in the case of a generic comparer used to sort a collection or a list.

Consider the following:

List<Widget> widgets = GetWidgetsListFromSomewhere();
// Sort widgets by ID

widgets.Sort( new MemberComparer<Widget>("ID") );
// Now re-sort widgets by Name

widgets.Sort( new MemberComparer<Widget>("Name") );

You can see how easy this makes it to sort your collection based on a dynamic property or field. For example, you could easily wire this up to a UI to allow for fast sorting based on the column a user clicked on.

Here is the code for a simple MemberComparer class:

Note: This could easily be extended to support chaining of fields and sort directions together.

public class MemberComparer<ObjectType> : IComparer<ObjectType>
{
    private delegate int CompareDelegate(ObjectType x, ObjectType y);
    private CompareDelegate _compare;

    public MemberComparer(string memberName)
    {
        _compare = GetCompareDelegate(memberName);
    }

    public int Compare(ObjectType x, ObjectType y)
    {
        return _compare(x, y);
    }

    private CompareDelegate GetCompareDelegate(string memberName)
    {
        Type objectType = typeof(ObjectType);

        PropertyInfo pi = objectType.GetProperty(memberName);
        FieldInfo fi = objectType.GetField(memberName);
        Type memberType = null;
        bool isProperty = false;

        if (pi != null)
        {
            if (pi.GetGetMethod() != null)
            {
                memberType = pi.PropertyType;
                isProperty = true;
            }
            else
                throw new Exception(String.Format(
                    "Property: '{0}' of Type: '{1}' " + 
                    "does not have a Public Get accessor",
                    memberName, objectType.Name));
        }
        else if (fi != null)
            memberType = fi.FieldType;
        else
            throw new Exception(String.Format(
                "'{0}' is not a Public Field or Property" + 
                " with a Get accessor for Type: '{1}' ",
                memberName, objectType.Name));

        Type comparerType = 
          typeof(Comparer<>).MakeGenericType(
          new Type[] { memberType });
        MethodInfo getDefaultMethod = 
          comparerType.GetProperty("Default").GetGetMethod();
        MethodInfo compareMethod = 
          getDefaultMethod.ReturnType.GetMethod("Compare");

        DynamicMethod dm = 
           new DynamicMethod("Compare_" + memberName, typeof(int),
           new Type[] { objectType, objectType }, comparerType);
        ILGenerator il = dm.GetILGenerator();

        // Load Comparer<memberType>.Default onto the stack

        il.EmitCall(OpCodes.Call, getDefaultMethod, null);

        // Load the member from arg 0 onto the stack

        il.Emit(OpCodes.Ldarg_0);
        if (isProperty)
            il.EmitCall(OpCodes.Callvirt, pi.GetGetMethod(), null);
        else
            il.Emit(OpCodes.Ldfld);

        // Load the member from arg 1 onto the stack

        il.Emit(OpCodes.Ldarg_1);
        if (isProperty)
            il.EmitCall(OpCodes.Callvirt, pi.GetGetMethod(), null);
        else
            il.Emit(OpCodes.Ldfld);

        // Call the Compare method

        il.EmitCall(OpCodes.Callvirt, compareMethod, null);
        
        il.Emit(OpCodes.Ret);

        return (CompareDelegate)dm.CreateDelegate(
                           typeof(CompareDelegate));
    }
}

Assuming you want to sort the Widget class, the CompareDelegate that gets dynamically created contains the dynamic equivalent of the following code:

// To Sort by Name property

public int Compare(Widget x, Widget y)
{
 return System.Collections.Generic.Comparer<string>.Default.Compare(
                                                            x.Name, y.Name);
}
// To Sort by ID property

public int Compare(Widget x, Widget y)
{
 return System.Collections.Generic.Comparer<int>.Default.Compare(x.ID, y.ID);
}

Conclusion

There are many other places that this concept can be used in place of the old slow method of reflection. With this article, I have only scratched the surface of what can be done. Hopefully, I have at least given some insight into how powerful Reflection.Emit can be. I leave it up to the reader, however, to find other places that they might be able to use similar code and/or concepts.

History

  • 07/04/2006 - Updated code to also work with fields, and added a generic comparer example.
  • 06/23/2006 - Created initial version.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here

About the Author

Stephen Erisman


I am currently working as an Enterprise Architect at TicketsNow.com.

I have been designing and developing web/windows based software applications and utilities for 8+ years.

And here is a random picture of my dog. Wink
Occupation: Web Developer
Location: United States United States

Other popular C# articles:

Article Top
Sign Up to vote for this article
You must Sign In to use this message board.
FAQ FAQ Noise ToleranceSearch Search Messages 
 Layout  Per page   
 Msgs 1 to 25 of 32 (Total in Forum: 32) (Refresh)FirstPrevNext
GeneralMemberComparer and LINQmemberAnthony Bouch3:58 29 Jun '08  
GeneralSmall addition to DynamicPropertyManagermemberAnastasiosyal3:25 22 Jun '07  
GeneralDynamic types?memberMaidenGuy0:50 14 Jun '07  
AnswerRe: Dynamic types?memberStephen Erisman12:17 15 Jun '07  
GeneralHow about SetmemberScottVB4:57 24 Apr '07  
GeneralCultureInfo aware MemberComparer class helpmemberNikolaj Lynge Olsson11:34 28 Feb '07  
NewsProblems with structs (and solved!)memberunbird3:58 16 Feb '07  
GeneralRe: Problems with structs (and solved!)memberStephen Erisman12:06 16 Feb '07  
GeneralRe: Problems with structs (and solved!)memberdavojc3:02 14 Feb '08  
GeneralSetting the values of propertiesmembersma23:24 29 Nov '06  
GeneralRe: Setting the values of propertiesmembermgaerber0:10 18 Dec '06  
QuestionRe: Setting the values of properties [modified]memberDigital Ric17:30 13 Jun '07  
GeneralRe: Setting the values of propertiesmemberpsamwel18:36 3 Dec '07  
Questiondotnet 1.1memberaibo1:30 8 Aug '06  
AnswerRe: dotnet 1.1memberStephen Erisman5:19 8 Aug '06  
QuestionRe: dotnet 1.1memberaibo5:46 8 Aug '06  
QuestionNested objectsmemberMikeonn3:38 11 Jul '06  
AnswerRe: Nested objectsmemberStephen Erisman5:38 11 Jul '06  
QuestionFieldInfo not passed to Ldfld?memberNathan Baulch19:33 6 Jul '06  
AnswerRe: FieldInfo not passed to Ldfld?memberStephen Erisman6:43 7 Jul '06  
QuestionPurposememberTheSire0:33 4 Jul '06  
AnswerRe: PurposememberStephen Erisman13:44 4 Jul '06  
AnswerRe: PurposememberNordin Rahman20:06 23 Aug '08  
GeneralA better way...memberJ. Dunlap20:13 23 Jun '06  
GeneralRe: A better way...memberStephen Erisman6:30 24 Jun '06