Controlling memory management

  • Thread starter Thread starter Tushar
  • Start date Start date
T

Tushar

Hi,
I have also noticed this. But looks like its the optimization which windows
do when UI is not visible. Why need to hold UI objects in memory when they
are not visible. And these objects are restored when you restore the window.
This happens in Win2k also.
Also noticed... that lighter the UI, lesser is the variation in the memory.

-Tushar
 
Hello group,

We're working on a fairly large application. We got to the point when the
memory consumption gets sensible; sometimes we have to plant GC.Collect
calls for this.

However, we noticed an interesting phenomenon. The amount of allocated
memory is immediately drastically reduced when the application is minimized
and then restored back. Looks like the OS (Windows XP in my case) also has
some kind of garbage collector which is called when the window state changes
this way.

Two questions:
1. Did anyone else experience this?
2. Is there any possibility to control this?
 
This is something that exists for several years on NT class OS'ses (NT4
SP3), a windows application that get's minimized is considered non-active
(idle), and the OS is aggressively reducing the Working set of the
application. This is something you shouldn't do yourself as it will only
result in excessive page-in page-out IO activity which hurts performance
badly.

Willy.
 
Thanks for the replies guys.

But I meant that after I minimize AND restore back, the amount of allocated
memory is still much less than it was before.
 
Back
Top