Suddenly aspnet_wp.exe memory builds up

A site we are moving from asp to asp.net has a weird problem. During slow
times it's fine and performs great, however when each server gets about 50
to 60 requests/sec, performance is still great but out of the blue the
memory usage goes from 200-300 mb aspnet_wp and keeps going until the
process gets recycled, it is then fine for a short while. We have made sure
there aren't any large datatables loading or any other sort of data that
could be building up. We also set the sql server to stop any with a cost
over 10 seconds for any connections coming from application. We can not
mimic this in our development environment, it only exists on our web farm of
three servers and it happens on all three servers sporadically. We can not
pin point it to any operation or page. However we are using a few COM
objects that have not been recoded in .NET yet such as jpeg manipulation and
encryption. Does anyone have any ideas how to pinpoint the problem, any ways
to determine what object or code is the culprit. This is still unnoticed by
our customers due to the sql state + load balancer and web farm.. but it
gets very expensive on the processors during busy times to have the
aspnet_wp restart as often as 10 minutes or so during heavy load times.

-Billare you disposing the unmanaged objects properly? a lot of the times, this
is the culprit. see about that first then have a look at the memory profiler
available from the framework to trace this issue. here is a link for further
troubleshooting
http://tinyurl.com/3dsxc

--
Regards,
Alvin Bruney
Got tidbits? Get it here...
http://tinyurl.com/3he3b
"Bill Green" <green_bill@.hotmail.com> wrote in message
news:O1Pzzvn3DHA.2612@.tk2msftngp13.phx.gbl...
> A site we are moving from asp to asp.net has a weird problem. During slow
> times it's fine and performs great, however when each server gets about 50
> to 60 requests/sec, performance is still great but out of the blue the
> memory usage goes from 200-300 mb aspnet_wp and keeps going until the
> process gets recycled, it is then fine for a short while. We have made
sure
> there aren't any large datatables loading or any other sort of data that
> could be building up. We also set the sql server to stop any with a cost
> over 10 seconds for any connections coming from application. We can not
> mimic this in our development environment, it only exists on our web farm
of
> three servers and it happens on all three servers sporadically. We can
not
> pin point it to any operation or page. However we are using a few COM
> objects that have not been recoded in .NET yet such as jpeg manipulation
and
> encryption. Does anyone have any ideas how to pinpoint the problem, any
ways
> to determine what object or code is the culprit. This is still unnoticed
by
> our customers due to the sql state + load balancer and web farm.. but it
> gets very expensive on the processors during busy times to have the
> aspnet_wp restart as often as 10 minutes or so during heavy load times.
> -Bill