Re: Small C# program takes up too much memory
- From: "Tom Porterfield" <tpporter@xxxxxxxx>
- Date: Wed, 21 Feb 2007 14:28:16 -0500
Chris Mullins [MVP] wrote:
While I agree with you 100% on every technical level, the user's
perception defines reality. Users see the big number in task manager and
get cranky. They see a small number, they're happy.
I really wish I had a better answer. For almost all the small client-side
stuff we do, this works well. Especially as these apps load, and don't
really do anything. They're doing almost no processing, no data base
stuff - they're just sitting idle and reporting that they're taking 20-50
megs of memory.
Running GC.Collect over & over doesn't even solve the problem - the app
still reports a huge amount of memory, and the users perception then is
that we suck.
Please - give me a better solution! :)
Believe it or not, when I ran into that I actually took the approach of education the user. It took a bit and not all go it, but most did and I no longer heard complaints on this.
--
Tom Porterfield
.
- References:
- Small C# program takes up too much memory
- From: elty123
- Re: Small C# program takes up too much memory
- From: Chris Mullins [MVP]
- Re: Small C# program takes up too much memory
- From: Willy Denoyette [MVP]
- Re: Small C# program takes up too much memory
- From: Chris Mullins [MVP]
- Small C# program takes up too much memory
- Prev by Date: Re: RedirectStandardOutput & OpenTextFile Conflict
- Next by Date: Re: lock statement question
- Previous by thread: Re: Small C# program takes up too much memory
- Next by thread: Re: Small C# program takes up too much memory
- Index(es):
Relevant Pages
|
