Re: Windows array allocation problem
- From: Roy Lewallen <w7el@xxxxxxxxx>
- Date: Sat, 29 Sep 2007 13:15:24 -0700
Tim Prince wrote:
The 2GB virtual space (3GB if you add /3GB boot switch) is occupied not
only by your arrays, but by the OS, its data tables, your program, ...
The available space has been decreasing as patches are added, with SP2
taking up a huge chunk. Not that we could advise you to run without the
patches.
Each Windows application is allotted a 2 GB virtual memory space. You're saying that each of those includes the operating system?
API function GlobalMemoryStatus or GlobalMemoryStatusEx returns both the total virtual memory (dwTotalVirtual or ullTotalVirtual) and available virtual memory (dwAvailVirtual or ullAvailVirtual). The total virtual value returned is 2 GB as expected. The available virtual is less than 2 GB, and I had thought that the amount used by the program, other arrays, and so forth had been subtracted, leaving the amount that's, well, available. But it isn't available for the allocation of the array. Which is my question. How much really is available for the allocation, how can I find out how much is, and why doesn't the GlobalMemoryStatus report the amount really available?
Roy Lewallen
.
- References:
- Windows array allocation problem
- From: Roy Lewallen
- Re: Windows array allocation problem
- From: Tim Prince
- Windows array allocation problem
- Prev by Date: Re: Windows array allocation problem
- Next by Date: Re: Windows array allocation problem
- Previous by thread: Re: Windows array allocation problem
- Next by thread: Re: Windows array allocation problem
- Index(es):
Relevant Pages
|