By default, Windows based operating systems have a limit of 2GB of address space per process.
With Windows 2000/2003 Server, Microsoft uses Intel PAE technology to overcome these limitations.
The switches are: /3GB, /PAE and /AWE
- /3GB allows up to 3 gigabytes of address space but only for executables that have been built for it.
- /PAE is the ability of the IA 32 processor to address more than 4GB of physical memory.
- /AWE API's allow a program to remap pieces of its 32-bit address space over larger amounts of memory.
Progress does not support these switches and API’s. They will not help to overcome the 2GB memory limitation per process on Windows platforms. This 2GB Virtual Address Space memory limitation is per process only. It will not prevent having several distinct databases processes allocating a total amount of memory that can go beyond 2GB, however a self-service client process connecting to more than one database still has the same virtual address space limit.
OpenEdge 10.1B introduced Improved shared memory segment allocation enhancements where a new database configuration parameter,
-shmsegsize, allows the shared-memory segment size to be set explicitly, where it was previously hard-coded to 128MB. For 32-bit systems, this means a 32-bit database can address fewer but larger shared segments (up to the size allowed by the operating system). When not specified this parameter is calculated. When the required memory exceeds 1GB, it is advisable to use a lower -shmsegsize.
