About memory usage...

**Xorcist** · 13-11-2002, 11:19 PM

Um... I just compiled it in Delphi 5.0, and using the Resource Manager (under Win98SE), it appears it only takes up 1.2MB of memory. Wonder if it might also have something to do with running under NT/XP?

**Alimonster** · 13-11-2002, 11:31 PM

Mine comes out as 992K of memory usage with Delphi 5 and Win2K. Still too much, mind you. I wonder how Delphi 6 affects things...

**Xorcist** · 14-11-2002, 04:26 AM

What sort of tools does everyone use to monitor system resources and profile their applications? Just interested as I've never used any myself.

**Mike** · 14-11-2002, 08:14 AM

I use only the XP's Task Manager, by default it doesn't show you how many handles or threads there are, but in View->Select Colums you can make it show various information, like how many I/O reads programs has done etc.

I installed Delphi3 and tried compiling the program: the executable came slightly bigger, it's 15 kb but the memory usage dropped to 616 kb. I think that's still too much for such a small app, but much less compared to program compiled with Delphi6.

**Viro** · 14-11-2002, 08:49 AM

I've just tried compiling the program using Delphi 7. I got a 13.5 KB app, and the runtime foot print was around 2.4MB. I tried fiddling with compiler options, and it didn't change a thing!! That is so weird. I would have expected that turning of all the debugging options would make the exe size smaller, but nope, that didn't do a thing.

**Armand** · 18-11-2002, 05:54 AM

Originally Posted by Mike

When I create a simple application like:

snip..

The executable is 6 kb, which is fine... But when I run the program, why an earth is takes 3 MB ram?

Okay.. I made the same app with Delphi 6 {on a win 2k box}.

The app took up of 808K mem when running acording to task manager.
It was (9,216 bytes) but 16.0 KB (16,384 bytes) size on disk.
I ran it throught code seluth and didn't find any allocated memory at all.

Id love to know where the bloat is coming from.

Armand.

Delphic · 18-11-2002, 10:50 PM

...

**raidos** · 12-12-2002, 10:32 AM

Program SmallApp;

function MessageBoxA(HWND: Cardinal; Msg,Title: pChar; Flags: Cardinal): Cardinal; stdcall; external 'User32.dll';
function SetProcessWorkingSetSize(hProcess: LongWord; dwMinimumWorkingSetSize, dwMaximumWorkingSetSize: LongWord): LongBool; stdcall; external 'kernel32.dll';
function GetCurrentProcess: LongWord; Stdcall; external 'kernel32.dll';
procedure Sleep(dwMilliseconds: LongWord); stdcall; external 'kernel32.dll';

begin
MessageBoxA(0,'Hello from a small app.','Small App',0);
SetProcessWorkingSetSize(GetCurrentProcess, $FFFFFFFF, $FFFFFFFF);
MessageBoxA(0,'Hello from a smaller app.','Small App',0);
SetProcessWorkingSetSize(GetCurrentProcess, $FFFFFFFF, $FFFFFFFF);
Sleep(30000);
end.

Neat huh ? =)

Don't know exactly why it shrinks the memory footprint....i assume it swaps unused data to disk or something but atleast it appears that the application uses a minimal amount of memory.

[EDIT]
Oh, and btw when needing a small application you should look into KOL
http://bonanzas.rinet.ru/
[/EDIT]

Regards
//raidos

**Alimonster** · 12-12-2002, 11:44 AM

From the help at MSDN:

If both dwMinimumWorkingSetSize and dwMaximumWorkingSetSize have the value -1, the function temporarily trims the working set of the specified process to zero. This essentially swaps the process out of physical RAM memory.

$FFFFFFFF = -1 (take 1, negate all bits, add one

). A handy thing to know if a parameter is expected to be unsigned and you have to pass in -1...