Bug 19291 - Performance issues
Summary: Performance issues
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: WCF assemblies (show other bugs)
Version: master
Hardware: Macintosh Mac OS
: Normal enhancement
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-04-25 02:27 UTC by ananth
Modified: 2017-09-06 16:55 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
results (13.87 KB, application/octet-stream)
2014-04-25 02:27 UTC, ananth
Details
test app (502.56 KB, application/x-zip-compressed)
2014-04-25 02:28 UTC, ananth
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report for Bug 19291 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description ananth 2014-04-25 02:27:20 UTC
Created attachment 6653 [details]
results

Hi Anuj,
 
Further to your email, we did a performance comparison of XMLSerializer vs DataContract with an iOS app running on the device, and the statistics are shared in the attached spread sheet ( “Stats with iOS sample app” worksheet). 
 
The application used to test is attached with this email. 
 
Before investing time to repeat this on Android  or Windows phone app, we thought it is important to understand the iOS numbers. 
 
Performance is *important* to us in this particular scenario, in fact the only factor that would decide for or against using DataContract. 
 
DataContract serialization is supposed to perform better (at least 10% faster according to official documentation), but the mono version appears to be otherwise - performing 1.5-3 times worse than XmlSerialization. 

Could you please investigate this issue and provide a resolution at the earliest? Like I said earlier we need to take these numbers to business to justify the changes, failing which business would not allow to go ahead with this change.
Comment 1 ananth 2014-04-25 02:28:24 UTC
Created attachment 6654 [details]
test app

test app