Nod 32 using less and less memory?

It is quite Funny. After i complained that why Doesn't NOD32 free up memory if i disable Imon and DMon. I relaise that NOD32 does actually uses less and less memory after a period of time.

From Starting the machine 17Mb ( which is quite distrubing ), it is now only using 3Mb after 4 days without restarting my computer.

So why is that? Why doesn't NOD32 just release it all when started?

 

which process are you referring to as having shrinking memory requirements:

nod32krn.exe

or

nod32kgui.exe

 

nod32krn.exe

it is now only using 7531k. Where when i start my computer it was 16xxxk.

 

It also happens on my computer

 

Doesnt seem to happen on my PC. At start it uses around 19mb of memory (i have win98se) after 4-5 hours it goes up to 20mb and just stays that way until i reboot.

 

This thread got me to checking. And it turns out that my memory is also going down. It started at at 17 MB and is now down to 14 MB.

 

I agreed.

On my Windows XP Pro, nod32krn.exe would take about 6MB short after booting (peak memory usage is around 19MB), and would continuously shrink to about 1~2MB in hours.

 

That's why I loved nod32 so much, for I've only 256M memory.

 

Yes.... Now after 1 day and a half running it is using 52xxK.

Last time after 4 days i had it around 2xxk..........
( Note: I only have Amon running and selected scan all files. )

Now that surely beats F-Prot in terms of memory usage.

But the questions is that why it take so long for the memory to decrease?

 

The memory management is controlled by the operating and NOT the applications that run on it. The operating system is most likely freeing resources after a while to "make room" for others.

 

Yeah...most applications will request as much memory as it thinks in might need when launch (especially if there is lots of free memory). Plus, alot of apps tend to check a whole bunch of things and load stuff in memory when first loaded. But it usually doesn't need all it requests. Later, it or the OS may release what it doesn't need once it's fully loaded and running for a while.

This is especially noticable with .NET apps. You can launch a .NET app that is only 100k that will use 20MB when first loaded. If you minimize it then it may release all but a couple 100k.

What it boils down to is...don't judge an application by the amount of memory after it's first launched. Let it run for a while and/or minimize it and see what changes in memory usage is made.

 

The advantage is not that NOD32 using less. But it doesn't add more in.
For example Outpost firewall uses less memory than any other firewall when first minimize. But the ram usage gradually build up again. This doesn't happen to NOD32. Which is a good thing.