[DUG] Memcheck

[Sean Cross - CRM]

Sometimes.  When you have 30 copies running on citrix, each taking up 50 meg...

I am going to trial compressing the working set immediately after loading, and then leaving it alone.  Once my app has loaded, it is using 26 meg of which 22 is not actually required.

Regards

Sean
-----------------------------
Sean Cross
Systems Development

CRM
PO Box 230
Napier
Phone:   06 835 5868
Mobile:  021 270 3466
Email:   sean.cross at crm.co.nz


 

> -----Original Message-----
> From: delphi-bounces at ns3.123.co.nz 
> [mailto:delphi-bounces at ns3.123.co.nz] On Behalf Of Kyley Harris
> Sent: Thursday, 1 December 2005 1:20 p.m.
> To: NZ Borland Developers Group - Delphi List
> Subject: Re: [DUG] Memcheck
> 
> Does anyone actually care about such matters in real working life?
> 
> I mean, it operating system managed memory. When it needs it, 
> it takes it back. One would hope and presume that it is 
> managing it in such a way as to appear efficient for speed 
> and allocations by not retaking memory pointers back from an 
> application that may well want them again.
> 
> On Thu, 01 Dec 2005 14:21:17 +1300, Stefan Mueller 
> <muellers at orcl-toolbox.com> wrote:
> 
> > You can do it manually (compressing the memory-creep) by calling:
> >
> > if Win32Platform = VER_PLATFORM_WIN32_NT then
> >     SetProcessWorkingSetSize(GetCurrentProcess, $FFFFFFFF, 
> $FFFFFFFF);
> >
> > This has the same effect like a minimize/maximize.
> >
> > Cheers,
> > Stefan
> >
> >
> _______________________________________________
> Delphi mailing list
> Delphi at ns3.123.co.nz
> http://ns3.123.co.nz/mailman/listinfo/delphi
> 
>