Try OpenEdge Now
skip to main content
Getting Started
Introducing OpenEdge Management and OpenEdge Explorer : OpenEdge Management CPU and memory requirements : Memory use
 

Memory use

OpenEdge Management memory utilization is directly related to the number and types of resources being monitored. The AdminServer with OpenEdge Management loaded but no resources defined requires 25MB to 35MB of RAM memory. This requirement can vary based upon the platform and the number of other OpenEdge products installed.
As you add resources to OpenEdge Management, the memory requirements increase. Each monitored database requires about 2MB of memory. Other monitored resource types require much less, typically in the range of 10KB to 100KB per resource.
OpenEdge Management allows you to store the data being used for graphs. This increased storage can cause a significant increase in memory usage.
Factors you can control to manage OpenEdge Management memory utilization include:
*The number of monitored resources —If OpenEdge Management is consuming an unacceptable amount of memory, you can reduce the number of monitored resources. You can also choose to install an instance of OpenEdge Management on a nonproduction host and use that host to monitor network and log file resources. This would remove the load from your production hosts, leaving on them only the monitoring of local system resources and databases.
*Use of the OpenEdge Management remote database monitoring agent — Using an instance of OpenEdge Management on a nonproduction host in conjunction with the remote database monitoring agent will allow you to greatly minimize overhead on your production systems. In this configuration, the majority of OpenEdge Management activity is off-loaded to a nonproduction host. Only the overhead of the remote database agent will be incurred on your production systems. This overhead is minimal.
*Adding remote monitoring on the OpenEdge Management machine — The addition of remote monitoring will substantially increase memory use.
*Working with the Database Administration Console — When you are working with the Database Administration Console (and depending on how it is configured), there may be one or more copies of _progress.exe actively running. These copies of _progress may connect and disconnect from any monitored databases to perform tasks needed for the Database Administration Console.