Re: Memory issue
* Balog Pal:
"Alf P. Steinbach" <alfps@start.no>
You set the swap file size to 0 and there is no swap, ever.
First, very few would use a program that modified the system page file
settings just to simplify its own internal memory handling.
Err, I did not mean the program, I meant YOU. :) The user or admin of the
machine. A program certainly has no business with swap or the memory or
anything.
In that case it's irrelevant.
Second, there's no way to do it in standard C++.
Third, the context wasn't about how to turn page file usage off, it was
about what happens on a system with enough memory but page file usage
enabled.
Possibly I misread, the context I was aware of was what happens when memory
is exhausted. As it seen from a C++ program's perspective, that just keeps
adding items to a vector, and see what eventually happens.
You claimed that the system will most likely crawl before anything else is
observed. I didn;t notice anyone injected a restriction of the system to
include a swap configured way beyond physical memory, and the physical
memory set way lower than the process' address limit.
A swap file (a.k.a. page file) isn't meaningful if physical memory alone is
enough. Any claim that the usual configuration is to not have a swap file is
just incorrect. At this point in time the usual PC configuration is perhaps not
the most sensible one, but it was, and will again be.
And before and after this point in time (except that we've had this transient
situation once before) most PCs have had and will again have far less physical
memory than the available address space for ordinary apps.
So both those that you call "restrictions", as if they were unusual and quite
unexpected features to consider, are the normal state of affairs.
Cheers & hth.,
- Alf