Memory Usage

Jul 21, 2008 at 5:45am
Hello,

I have a program that I am writing and would like to know the memory requirements that it needs. Is there a way of determining this other than examining it through another process (like Windows Task Manager)? I need to publish its memory requirements and recommendations. Also, how can I tell the program is needing use of a swap file? Any help would be greatly appreciated.

Thanks
cppdna
Jul 21, 2008 at 7:52pm
Swap file will be dependent on the amount of RAM the target system has.

You can get the memory requirements 2 ways.
1) Run the application and monitor it's memory usage. Through task manager or performance monitor.

2) Use a professional (or possibly open source) profiling tool. This will keep track of the memory usage of your application and report it back to you once you have finished execution.

Without actually running the application it's impossible to estimate the amount of memory usage. Especially if you are using a lazy-allocation style design pattern.
Jul 23, 2008 at 9:03pm
@Zaita

So there is no way to report on the memory usage from within the application itself? Can you recommend a profiling tool that would be good to use? Thanks.

cppdna
Jul 23, 2008 at 9:26pm
I use AQTime at work. But it's like $600USD per user. http://www.automatedqa.com/products/aqtime/

It maybe a bit over-kill for what you are after. Personally. I'd look at the Task Manager when you have the application in use and add 25% to that. Then say thats the Min requirements memory-wise.
Jul 23, 2008 at 10:37pm
Process Explorer not only tells you the current memory usage, it also tells you the peak usage, it plots it on a graph along with CPU usage and IO bytes/unit of time. It also reports a myriad of other parameters, such as total CPU time (both in kernel and user), virtual memory usage, threads, TCP/UDP connections, etc.
Jul 23, 2008 at 10:38pm
@helios: I agree that Process Explorer/Task manager should be more than sufficient.

AQTime would be overkill :P I use it for performance turning down to the millisecond, and for memory leak detection.
Topic archived. No new replies allowed.