I’ve had a couple of complaints that one of our managed apps is using 20-25Mb of RAM. I normally push back and say that memory’s cheap; get over it.
Is this reasonable for a Windows Forms app?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve had a couple of complaints that one of our managed apps is using 20-25Mb of RAM. I normally push back and say that memory’s cheap; get over it.
Is this reasonable for a Windows Forms app?
20-25MB is nothing.
The .Net framework doesn’t always recycle RAM right away anyway. Over time I’ve seen apps grow to peak at a few hundred MB of RAM during an ‘expensive’ process, and then just sit there even after the ‘expensive’ process finished. However, this is misleading. The app wasn’t using this RAM. It’s just that the garbage collector hasn’t seen a need to collect a lot of old RAM yet. If the operating system had need of that RAM rest assured that it would be collected. The idea that an app should only use a few hundred K at most just doesn’t apply in a managed environment — for operating system processes , yes. For native apps, maybe. But not managed code. Otherwise you just end up with systems that have a full GB or more of RAM that just sits idle.