"Ales Pour" <ales.pour@systinet.com> wrote in message
news:%23vBGsU1tEHA.224@TK2MSFTNGP15.phx.gbl...
> Hello.
>
> I've tried to profile ws client with CLR Profiler and I'm surprised with
> results. Calling simple method which echoes string that was sent to it
> 1000 times causes allocation of 33 MB (ok, not a big deal ;-) ), what is
> worse that over 8 MB was rellocated (most of them byte arrays and strings)
> and gc for gen 1 was called 42 times. I'm not expert in interpreting the
> the profiler results, but it appears to me that most byte arrays that get
> into gen 1 are memory chunks of request and response streams.
>
> I wonder if there's a way to improve the performance of ws invocation
> (perhaps using own WebRequest/WebReponse and doing some trick in those
> subclasses, or anything else)? Thanks!
>

> Sure you could do alot to reduce memory allocation in this scenario, but
> you would loose the ease-of-use of invoking a webservice through a web
> reference.
>
> If you want to try it, here's how:
>
> Navigate to the myWebService.asmx page and examine the soap message it
> requires. It's just an HTTP request: nothing magical. Cut and paste the
> soap message for each method into your code. Then recode your methods to
> stream that soap message over a HTTPWebRequest's NetworkStream to the
> server and use an XmlReader to read the streaming result and extract the
> return values. In all this could be done with very little memory
> allocation, and not really too much code, but at the cost of ease of use
> and maintainence.
>
> David
>