Aspnet Worker Thread Memory Usage

[jld]

Hi,

I developed an asp.net based eCommerce Website for a client and it is
hosted at discount asp.

The site is quite interactive, queries a database a lot and uses
ajax.asp.net to spice up interactivity.
The service suffers from a lot of restarts since discountasp enforces
a 100mb per worker thread limit and when you top it, the service gets
restarted. When there is a lot of traffic on the site, this happens
almost every other minute and users see an unwelcoming "service
unavailable" quite often.

Now I already tried to strip down memory usage, by eliminating almost
all session objects, by using datareaders instead of datasets and by
by employing a very disconnected, database based "state" architecture,
but I still cannot keep MB usage under 100mb.

So I am about to tell my client that he will need to move to a host,
that does not have such a strict memory policy, maybe a virtual host
on a machine with few users.

But just to double check: how does memory usage on your sites look
like? Could you check in task manager, what asp net uses when you view
a single site/application, and the tell me, together with some info
about the site's complexity?

I would be very glad, to have some numbers, that could tell me, if the
host just is not thought for heavier usage or if I am just doing
something stupid that no one else does.

Jan

 

[Guest]

You can track such events on a hosted account with some of the ASP.NET event
providers. Here is an article that touches on some of this, including
tracking app recycles.

http://www.eggheadcafe.com/tutorial...f2-e68b28dbe836/restart-aspnet-apps-prog.aspx

Aside from that, cache everything that you can to cut down on database
usage. Failing that, you need to consider a different host. I've used
CrystalTech with excellent results, and also gate.com with good results and
few restarts.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder(BETA): http://www.blogmetafinder.com

 

[Otavio Decio]

Aside from that, cache everything that you can to cut down on database

usage.

Not sure how that will help on his memory usage problem. One thing you might
try is to force garbage collection once in a while. Also .NET may leak
memory, see if you can find potential culprits.

I agree with considering a different host, though. If you have so much
usage, maybe it is time to move up from your discount provider.

Otavio