Consultor Eletrônico

Status: Verified

GOAL:

Why is the Progress OpenEdge client executable's memory footprint larger than previous versions' memory footprint?

GOAL:

What is the reason for the increased memory size of the _progres executable in OE Release 10?

GOAL:

What are the client memory utilization changes that one should expect to see when upgrading from Progress version 9 to Release 10?

GOAL:

Why is 10.1A using more memory than version 9?

GOAL:

Why is 10.1A using more memory that 10.0B?

GOAL:

Why does OpenEdge 10.1A use more memory than previous releases?

FACT(s) (Environment):

OpenEdge 10.1A
All Supported Operating Systems
OpenEdge Database Category: Performance

FIX:

There is an increase of approximately 30% in memory size consumption of the Progress character client process (_progres) in OpenEdge 10.

This size increase can be attributed to:

- more code went into the executable
- more data (static variables, etc) are in the executable

Here is some data that was collected during tests on Progress internal machines:

On Solaris

101a 32bit 64bit % Increase
_progres 12758652 (12 MB) 14942920 (15 MB) 17%
100b
_progres 11631056 (11 MB) 15296816 (15 MB) 31%

On HP

101a 32bit 64bit % Increase
_progres 9752576 (9 MB) 11780496 (11 MB) 20%
100b
_progres 8613888 (8 MB) 11269832 (11 MB) 30%

On AIX

101a 32bit 64bit % Increase
_progres 11367517 (11 MB) 12706151 (12 MB) 11%
100b
_progres 9785093 (9 MB) 11244402 (11 MB) 15%


Memory size comparison of Progress 9.1E vs. OpenEdge 10.x on SUN Solaris:

9.1E 10.0B 10.1A
32bit _progres 9325664 11632608 12758044
64bit _progres 11338728 15298680 14942208
9.1E 32-BIT vs. 10.0B 32-BIT = 24% larger than 9.1E
9.1E 64-BIT vs. 10.0B 64-BIT = 35% larger than 9.1ESPAN>


What is not included in these findings are things like amount of dynamic memory (heap from a malloc() call), which most likely increased as well..