 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / ASP.NET / Web Services / February 2006Optimizing webservice call which are returning datasets
Hi all, Application environment : VB.Net desktop application,.NET 1.1 Framework, VS 2003. communicates between the database and the application is done over webservices using ADO.NEt Datasets. Returned dataset is Gzip compressed and is then decompressed on the receiving side. Every thing works good, the problem is that it takes a lot of time for the webservice to return my data filled dataset even if there is not much data, i thnk the reson being 1. serilization of dataset is expensive 2. datset is all XML and so even XML tags add to the space as well. Even though this is all compressed but even then it is taking long and their always is room for improvment, can any one out there tell me the best strategy for trasferring the data over the webservice i.e should I replace the dataset with another object for transmiting it over the webservice OR is there any other way to make sure datasets are tranmitted faster. thanks Sameer Maybe the delay is caused by the compression or fetching the data rather than the transmission size/time? > Hi all, > [quoted text clipped - 22 lines] > > Sameer Ken , thanks for your reply, nope, if not for compression it takes a long time, like if with compression it takes 1 minutes then without cmpression it takes 3-4 minutes. And there really is not that much data in the dataset, so again i am trying to blame XML tags for incresing the size of the data. So does any one out there know a better alternative to passing data over the webservice instead of passing a dataset. thanks > Maybe the delay is caused by the compression or fetching the data rather > than the transmission size/time? [quoted text clipped - 25 lines] > > > > Sameer Remoting is an excellent way to transfer data efficiently. It doesn't have the overhead of SOAP but it isn't as universal. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cp connetremotingoverview.asp > Ken , thanks for your reply, > nope, if not for compression it takes a long time, like if with [quoted text clipped - 43 lines] >> > >> > Sameer could be very well possible, but this application is pretty huge and is already done, i am just optimizing it, i would want to get suggestions considering webservices only. let me know if you got one. thanks > Remoting is an excellent way to transfer data efficiently. It doesn't have > the overhead of SOAP but it isn't as universal. [quoted text clipped - 48 lines] > >> > > >> > Sameer When you say GZip'd - do you mean in the transport protocol (i.e. your [WebMethod] returns a DataSet), or are you explicitely serializing the object to a GZip stream yourself? If the latter, this could be part of the problem, as a: 1.1 DataSets have really bad binary serialization (i.e. it's just the same xml written in binary...), plus the lack of MTOM means you will be (base-64?) encoding the binary on top. Is this a possiblilty? Marc Marc, i am not explicity serializing it, also IIS 6.0 compresses the dataset and all i do is uncompress it, this is only increasing the performance and not decreasing it. Any other Suggestions of transfering the data over webservices instead of using a sending a data. thanks. > When you say GZip'd - do you mean in the transport protocol (i.e. your > [WebMethod] returns a DataSet), or are you explicitely serializing the [quoted text clipped - 4 lines] > > Marc OK, scratch that idea then... it was worth a shot. Beyond that... my only real advice in this scanario is to minimise what you are transferring... are there any columns with lots of text in them that the client doesn't need? Do you really need all the rows or could you use paging? That sort of thing. Your original post doesn't give any indication of what sort of size / complexity of DataSet we are talking about; if this is returning 15 DataTables (with complex relations) each with 40 columns and 10000 rows then yes, it will take a while. If you genuinely need all of the data at the client (and you can't cache it locally for whatever reason) then I'm not sure there are many alternatives under 1.1 and [WebMethod]. If you were in 2.0, you could consider using a GZip'd binary serialization of the dataset transferred via MTOM (WSE3) - this should (theoretically) take a lot less bandwidth. But according to the original post, you're not. <stumped/> Marc Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.