Boost performance with Pre-generated XmlSerializers

re: Boost performance with Pre-generated XmlSerializers

UK — Sun, 08 Feb 2009 22:57:02 GMT

You can find a tutorial on how to create the XmlSerializers for the crm web service manually on my blog.

re: Boost performance with Pre-generated XmlSerializers

goruiz — Tue, 10 Feb 2009 19:26:11 GMT

I find your tutorial very useful, I was not expecting to see such a huge benefit! (~12 seconds in your case).

Unfortunatelly you'd have to generate your own CrmService proxy which has the disadvantages you pointed out. If you could use the SdkTypeProxy and SdkTypeProxy.XmlSerializers that are shipped woth the product you'd only have to do step 10.

re: Boost performance with Pre-generated XmlSerializers

Gautam — Tue, 12 May 2009 21:03:04 GMT

Thanks for the article, very useful, I was also thinking whether we can create a pool of proxy objects so that we can re-use them(like Database Connection pool )... is it considered a best practice ?

re: Boost performance with Pre-generated XmlSerializers

Gregory E — Fri, 28 Aug 2009 00:49:22 GMT

I've duplicated your steps and am unable to achieve the startup time you have achieved.

My first step was to right a small console application with a tweak to the app.config so any temporary generated code is persisted after the application finishes and is placed in a different folder. (see Scott Hanselmans blog about this: http://www.hanselman.com/blog/ChangingWhereXmlSerializerOutputsTemporaryAssemblies.aspx)

//Using the Web Reference method

DateTime s1 = DateTime.Now;

new localhost.CrmService();

DateTime e1 = DateTime.Now;

double webReferenceTime = (e1 - s1).TotalSeconds;

//Using the Pre Compiled method

DateTime s2 = DateTime.Now;

new Microsoft.Crm.SdkTypeProxy.CrmService();

DateTime e2 = DateTime.Now;

double precompiledTime = (e2 - s2).TotalSeconds;

Test Run 1

------------

Web Reference (without generating XmlSerializer assemblies) - 9.15 seconds

Pre Compiled Assembly - 9.65 seconds

Looking at the directory that contains the temporary assemblies I can see 2 different temporary assemblies one for the web reference and one for the pre-compiled assembly

Test Run 2

------------

Web Reference (with generating XmlSerializer assemblies) - 4.37 seconds

Pre Compiled Assembly - 9.52 seconds

Looking at the directory that contains the temporary assemblies again I only see 1 temporary assembly which judging by the times in Test Run 2 would indicate that the Web Reference is using the pre-generated assembly correctly.

According your blog post as long as the Microsoft.Crm.SdkTypeProxy.XmlSerializers.dll is in the GAC and you are using the same processor architecture and version than the pre-compiled assembly should see a speed increase because it will use the XmlSerializers.dll. This is clearly not the case if you look at the times it takes to instantiate the first CrmService and the temporary files been generated.

Why isn't this working for me?

re: Boost performance with Pre-generated XmlSerializers

Gonzalo Ruiz — Mon, 31 Aug 2009 18:10:26 GMT

The only reason I know for which this would not work is if the assembly Microsoft.Crm.SdkTypeProxy.XmlSerializers.dll was generated against a different version of the assembly Microsoft.Crm.SdkTypeProxy.dll that you are using.

Microsoft.Crm.SdkTypeProxy.XmlSerializers.dll remembers the exact assembly Id of its parent assembly, a way to find out whether they match is to disassemble both assemblies. If both of these assemblies are taken from the same source then they should come from the same build so the assembly Id should match.