Kbase 17862: -mmax: When will we exceed it and when do we use sort files?
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  5/10/1998 |
|
-mmax: When will we exceed it and when do we use sort files?
-mmax: When will we exceed it and when do we use sort files?
Maximum Memory (-mmax): This startup parameter is the initial amount
of memory allocated for r-code segments.
"Progress dynamically allocates space for r-code segments in the
execution buffer as needed. When memory allocation reaches the value
specified by the Maximum Memory (-mmax) value, Progress writes
non-active segments to the sort file to make room for new active
procedures."
So, Progress will use the amount of memory that we predetermined by
the (-mmax) parameter. Once this value has been used we will then
swap out as many r-code segments, as necessary, to free up additional
space. This is done so that we can read in additional r-code segments.
R-code segments that are not being actively used can be swapped out
to a sort file to free-up additional memory.
If a procedure is run to completion (and is not considered to be
persistent) Progress will not redeem the memory for the r-code until
we need it. The reason is many times the same procedures are run over
and over again. Progress will lock any action code segments that are
on the "call stack", which are persistent and/or the text segment.
The remaining r-code segments are considered to be available to be
swapped out if necessary. The r-code segments that are least recently
used will be the first to be swapped out to the sort file when needed.
When we have been forced to swap out r-code segments (that are
considered to be available) and we need to exceed the -mmax value
Progress will increase this value and then display a warning message.
WARNING: -mmax exceeded. Automatically increasing from <old value>
to <new value> (5409) (Message is only displayed in Version 8+)
To prevent this value from being exceeded you can use the -hardlimit
startup parameter. (Please refer to your System Administration
Reference for more information regarding this parameter.)
(The -hardlimit parameter was introduced in version 8 of Progress)
CSG 4/21/98
Resources: System Administration Reference
Progress Software Technical Support Note # 17862