Accumulating Memory Usage

[BrewManNH]

_WinAPI_EmptyWorkingSet is not a good idea. It pages data out of memory to the hard drive, which means that it will cause the programs to run slower. Memory is faster than reading/writing from a disk. There's absolutely NO reason to try to reduce virtual memory size, virtual memory is your page file on the hard drive. The only way to reduce virtual memory is to change your page file size, which limits your programs as to how much it can page to the disk.

The 2 processes you're trying to accomplish are actually in exact opposition to each other, either you want the data in faster memory or you want it on the hard drive in the page file, trying to reduce both is foolish.

[masvil]

16 hours ago, BrewManNH said:

_WinAPI_EmptyWorkingSet is not a good idea. It pages data out of memory to the hard drive, which means that it will cause the programs to run slower.

I know what you mean, but I have some infinite loops progressively eating memory. So after some hours they reach a couple of GBs of ram and the hosting machine starts to be negatively affected (of course). I know I should optimize the code instead of doing that _WinAPI_EmptyWorkingSet trick once a minute, but I still can't do it. Do you think this is the case _WinAPI_EmptyWorkingSet is the best temporary choise?

 

Quote

There's absolutely NO reason to try to reduce virtual memory size, virtual memory is your page file on the hard drive.

I got it, thank you for clarification.

[BrewManNH]

I don't think it's a good choice for anything. Figure out why you have a memory leak before artificially trying to hide the leak.