From: Adrian Tarjoianu on 2 Jun 2010 15:31
At the moment I am interested only in the IIS hosting approach. We are not
interested in self hosting yet.
Also, I didn't use any network tracing tool. netTcpBinding is 70% slower
If I use netTcpBinding aren't the DataSets binary serialized by default? If
no then how could I configure them with binary serializer?
""Steven Cheng"" <stcheng(a)online.microsoft.com> wrote in message
> Hi Adrian,
> So even if you set the DataSet to use binary serialization format the
> is still not quite good? Have you tried different hosting approaches such
> as using self-hosting (in a console application) or move to a different
> server to see whether there is any difference?
> Generally speaking, since WCF netTcpBinding naturally use binary encoding
> and DataSet (can be set to use binary serializer), the problem should not
> be no worse than the asmx webservice which use text based encoding on
> DataSet. Have you tried using some network tracing tools like netmon or
> tcp trace to capture the data transferred at the transport layer to get
> actual binary data size sent over wire?
> Steven Cheng
> Microsoft MSDN Online Support Lead
> Delighting our customers is our #1 priority. We welcome your comments and
> suggestions about how we can improve the support we provide to you. Please
> feel free to let my manager know what you think of the level of service
> provided. You can send feedback directly to my manager at:
>>From: "Adrian Tarjoianu" <adrian(a)usoffice.fareportal.com>
>>Subject: Re: hosting WCF service - netTcp binding - Server Application
>>Date: Thu, 27 May 2010 13:44:29 -0400
>>As per this thread, there are not any solution for transfering big
>>DataSets/DataTables via WCF.
>>Excluding the schema is not a solution. Also, because I use NetTcpBinding
>>protocol I cannot change the serialiazer type.
>>Do you have any other solutions?
>>""Steven Cheng"" <stcheng(a)online.microsoft.com> wrote in message
>>> Hi Adrian,
>>> As for DataSet, it seems .NET 3.5 add binary serialization for it so as
>>> improve serialization performance since for text message encoding cases,
>>> large dataset will be converted from binary byte to text format which
>>> increase the data size. Also, when using binary format serialization,
>>> also need to change the message encoding type from text to binary or
>>> of your binding. Here is a former thread mentioned transfering large
>>> dataset in WCF:
>>> #Passing 3MB DataSet via WCF - Best Practice