locked
Question on performance of ADO.NET Data Service deserialization RRS feed

  • Question

  • Hi there,

    I see in this forum you have a post .NET and ADO.NET Data Service Performance Tips for Windows Azure Tables. In the post you have a point #3: To improve performance of ADO.NET Data Service deserialization, in which you mentioned

    "When you execute a query using ADO .Net data services, there are two important names – the name of the CLR class for the entity, and the name of the table in Windows Azure Table. We have noticed that when these names are different, there is a fixed overhead of approximately 8-15ms for deserializing each entity received in a query."

    The post was written last year, so I am just wondering if this is still the case with the overhead?  And you gave 2 solutions, one is "you have a Customer entity class, use "Customer" as the table name instead of “Customers”." Do I still need to have the table name the same as my entity class name?

    Thank you,

    Ray.

    Friday, December 10, 2010 4:19 PM

Answers