Enabling WSE 2.0 sp3 doubled my memory usage

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Dave Stienessen - 25 Jul 2005 23:35 GMT

Hi,
I created a web service that returns a large result set - our end-game web
service implementation will use WS-Policy to force a username token to be
present for user authentication so I really just need WSE for that, but...
My web service for better or worse can return some large result sets - in an
extreme test I ran (mainly to prove what I've suspected) I loaded about 150MB
of data and returned it as an xmldatadocument - I can set a breakpoint at the
return statement to monitor the memory utilization up to the point where I
hand it back to the framework to return to the caller and see that about
250MB or RAM is used - not too bad so far - here's where it gets interesting:
1. If WSE is not enabled, the return of the xmlDataDocument peaks the w3wp
worker process at about 430MB - high, but I can understand where it would
make a copy of the data to send it back to the caller
2. If I enable WSE (just check the 2 boxes, I didn't put the policy in place
yet) the same return for the same data runs the w3wp up to about 820MB!!!

What's up with that! 820MB of RAM to return 150 MB of data!! Or am I
missing something stupid?

Signature

Dave Stienessen

Reply to this Message

Julie Lerman - 02 Aug 2005 02:41 GMT

do you have tracing on in your wse application. I had left it on and it
brought my webserver to it's knees. When I turned the tracing off, all was
well again.

http://www.thedatafarm.com/blog/PermaLink.aspx?guid=9496f210-1292-4c1b-923c-5775
cab385f1

hth
Julie Lerman

> Hi,
> I created a web service that returns a large result set - our end-game web
[quoted text clipped - 19 lines]
> What's up with that! 820MB of RAM to return 150 MB of data!! Or am I
> missing something stupid?

Reply to this Message

Dave Stienessen - 02 Aug 2005 13:27 GMT

No - tracing in WSE is off - this really worries me - I want WSE for the
policy and security enforcement, but even if I change this service to return
smaller batches of data, this memory usage is going to kill scalability.

Signature

Dave Stienessen

> do you have tracing on in your wse application. I had left it on and it
> brought my webserver to it's knees. When I turned the tracing off, all was
[quoted text clipped - 28 lines]
> > What's up with that! 820MB of RAM to return 150 MB of data!! Or am I
> > missing something stupid?

Reply to this Message

Julie Lerman - 02 Aug 2005 14:36 GMT

okay next question - is the 150MB being returned as a message or as a DIME
attachment? That's huge. Are you securing the 150MB (encrypting or signing
it?) Do you need to?

Also - MTOM (replaces DIME in WSE 3.0) specifically addresses resource
issues when returning large amounts of data. What are the chances of you
being able to leverage that (only works with vs2005...)

I do not have experience transferring more than about 2-5 MB back from my
web services. It is encrypted and signed but it is also compressed. So I am
not going to be the right person to help you out with this one, sorry to
say.

It *is* a known problem (example:
http://www.dotnet247.com/247reference/msgs/30/153747.aspx).

But I don't happen to know how people are getting around it (DIME just
sucks) with WSE 2.0.

Julie

> No - tracing in WSE is off - this really worries me - I want WSE for the
> policy and security enforcement, but even if I change this service to
[quoted text clipped - 44 lines]
>> > What's up with that! 820MB of RAM to return 150 MB of data!! Or am I
>> > missing something stupid?

Reply to this Message

Enabling WSE 2.0 sp3 doubled my memory usage

Free Magazines