hosting WCF service - netTcp binding - Server Application Unavaila
in [IIS]
|
From: Adrian Tarjoianu on 2 Jun 2010 15:31 Hi Steven, 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 than asmx If I use netTcpBinding aren't the DataSets binary serialized by default? If no then how could I configure them with binary serializer? Thank you, Adrian ""Steven Cheng"" <stcheng(a)online.microsoft.com> wrote in message news:YxylwhTALHA.5808(a)TK2MSFTNGHUB02.phx.gbl... > Hi Adrian, > > So even if you set the DataSet to use binary serialization format the > speed > 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 > the > actual binary data size sent over wire? > > Sincerely, > > 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: > msdnmg(a)microsoft.com. > > > -------------------- >>From: "Adrian Tarjoianu" <adrian(a)usoffice.fareportal.com> > <ergtd7y#KHA.2348(a)TK2MSFTNGHUB02.phx.gbl> >>In-Reply-To: <ergtd7y#KHA.2348(a)TK2MSFTNGHUB02.phx.gbl> >>Subject: Re: hosting WCF service - netTcp binding - Server Application > Unavaila >>Date: Thu, 27 May 2010 13:44:29 -0400 > >> >>Hi Steven, >> >>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? >> >>Thank you, >>Adrian >> >>""Steven Cheng"" <stcheng(a)online.microsoft.com> wrote in message >>news:ergtd7y%23KHA.2348(a)TK2MSFTNGHUB02.phx.gbl... >>> Hi Adrian, >>> >>> As for DataSet, it seems .NET 3.5 add binary serialization for it so as > to >>> improve serialization performance since for text message encoding cases, >>> large dataset will be converted from binary byte to text format which > will >>> increase the data size. Also, when using binary format serialization, >>> you >>> also need to change the message encoding type from text to binary or >>> Mtom >>> of your binding. Here is a former thread mentioned transfering large >>> dataset in WCF: >>> >>> #Passing 3MB DataSet via WCF - Best Practice >>> > http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/088d0c74-6568-4496- >>> 8bfa-4ccf3a1ea851 >>> >>> Since > |