J
jdlwright
Hi, a customer is using our fairly memory intensive web app. in a
shared hosting environment
and the other day their host 'banned' (I think they just killed the
process) them for memory abuse.
Our app. has been profiled with SciTech's Mem Profiler, and it seems
that some of the issues relate to .NET bugs, but are alleviated by use
of System.GC.Collect(). I'm under the impression that it's generally
bad form to call this yourself, but at the same time, it strikes me
that the GC probably doesnt realise it's in a shared hosting
environment and there is happy to use up as much memory as it likes.
Possibly the host could do a better job of configuration(?), but that
doesnt really help much since we can't go around telling customers to
tell their hosts to sort out their config -> good way to lose a
customer.
So question is; what are the cons of calling Collect(), are they just
speed related?
Any tips would be welcome
Thanks
Jim
shared hosting environment
and the other day their host 'banned' (I think they just killed the
process) them for memory abuse.
Our app. has been profiled with SciTech's Mem Profiler, and it seems
that some of the issues relate to .NET bugs, but are alleviated by use
of System.GC.Collect(). I'm under the impression that it's generally
bad form to call this yourself, but at the same time, it strikes me
that the GC probably doesnt realise it's in a shared hosting
environment and there is happy to use up as much memory as it likes.
Possibly the host could do a better job of configuration(?), but that
doesnt really help much since we can't go around telling customers to
tell their hosts to sort out their config -> good way to lose a
customer.
So question is; what are the cons of calling Collect(), are they just
speed related?
Any tips would be welcome
Thanks
Jim