Kbase P131962: What is the status of support for HP-UX's Memory Windows feature?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
What is the status of support for HP-UX's Memory Windows feature?
GOAL:
Are HP's Memory Windows supported by OpenEdge?
GOAL:
Is it possible to increase the amount of shared memory available to processes through the use of HP-UX Memory Windows?
FACT(s) (Environment):
OpenEdge 10.x
HP-UX
FIX:
Memory Windows are a feature of HP-UX to allow 32-bit processes to use more than 1.75Gb of shared memory overall in the system.
There is no code in OpenEdge that knows about HP's memory windows.
Even if there were, it would not help much because memory windows does not increase the amount of shared memory that a 32-bit process can use. The default arrangement is that the 1.75 GB limit on shared memory is system-wide. In other words, if you have two unrelated programs that both use shared memory, the limit applies to both together.
What memory windows does is allow you to create multiple named windows within which related processes can access up to 1.75 GB of shared memory. So you could create two windows and run one of the two unrelated programs in each window, with a 1.75 GB limit on shared memory for each.
But anyhow, OpenEdge is not memory windows aware.
The only way to run programs that are not memory windows aware is to have their parent (perhaps a shell) create the window and specify the window when it runs the program. This is not practical in most OpenEdge environments because it requires every process to have the same parent. It could perhaps be made to work if all clients access the database over a network connection. Then broker, servers, biw, apw, aiw, etc could all be started by the same shell process. But: you couldn't use online backup, promon, etc.