Mail Archives: djgpp/2000/10/29/01:58:24
On Sun, 29 Oct 2000, Damian Yerrick wrote:
> Found "Unused physical memory".
That's the one.
> >when you, e.g., compile a large program.
>
> 34 KB of C source plus Allegro headers large enough?
Yes.
> Anyway, I tried it (through make), and it dipped about 3 or 4 MB and
> rose back. The "allocated" chart had a 4 MB high peak also.
That's normal behavior. It means that Windows makes up room in memory as
the need arises, by paging out whatever is there. cc1.exe is usually the
critter which needs between 4 and 6 MBytes (sometimes even 12MB or more)
to compile a program.
Once the program has enough memory to run, it will never page, unless you
also run one or more other memory-gobblers at the same time.
So, if we return to the original thread, the memory issue should not be
the reason for program's slowness, in configurations such as yours (and
mine).
> >and it includes VM. So it's not very interesting, since the Windows
> >swap file grows
>
> And shrinks. I also have "swapfile size" open, and it seems to track
> "allocated memory" pretty closely (lagging a bit but catching up when
> Windows compacts the swap file a minute later).
Yes, that's what I'd expect.
- Raw text -