Re: Windows array allocation problem

Roy Lewallen wrote:

I'm under
the impression that every 32 bit Windows program has an allocation of 2
GB of virtual memory. Isn't this the pool of memory the array is being
allocated within?
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.
.

Relevant Pages

  • Re: Windows array allocation problem
    ... I've just written a program which does nothing except call GlobalMemoryStatus to get the available virtual memory, then allocates an array to that size and in decreasing steps until STAT returns zero. ... The maximum allocation is consistently 146 MB less than the reported available virtual memory. ... So the phenomenon isn't due only to how Windows handles virtual memory but how the compiler handles it. ... The test shows that even for the simplest program, the Intel compiler doesn't allow allocating as much of the application virtual memory as the Compaq compiler does, at least not to one large array. ...
    (comp.lang.fortran)
  • Re: Windows array allocation problem
    ... If the required size exceeds the possible size, the program has internal virtual memory management to solve the problem in pieces, storing intermediate pieces on the disk. ... much is available for an actual allocation. ... since the array dimension and the determination of whether to use the virtual memory manager are presently being determined by the calling program and passed in. ...
    (comp.lang.fortran)
  • Re: GC performance - GC fragility
    ... Though the GC heap will look like one before compaction. ... allocation sizes to different "heap blocks", but it can't be IMHO generally be prevented. ... If you only have macro-fragmentation in the virtual memory space, you can operate with limited fragmentation-induced waste in the allocated memory space. ... that's because the concurrent GC can be gotten into a cycle of never ending GC compaction if your allocation rate exceeds or equals the compaction rate, a condition easy to reach when part of your allocated pool is swapped out. ...
    (borland.public.delphi.non-technical)
  • Re: Windows array allocation problem
    ... If I won't be able to allocate nearly all the available virtual memory, how can I determine in advance how much I *can* safely allocate? ... By "available virtual memory" I meant the amount that's actually available for use at the moment that the array allocation is made. ... My program has provision for approximately predicting the additional memory which will be used later in the program, and adjusts the allocation accordingly. ...
    (comp.lang.fortran)
  • Re: Windows array allocation problem
    ... By "available virtual memory" I meant the amount that's actually available for use at the moment that the array allocation is made. ... Functions that report the total amount ...
    (comp.lang.fortran)