Consultor Eletrônico

Performance issue with DEC Ultrix & 6.2L PROGRESS

This notebook entry describes a performance issue on DEC Ultrix 6.2L.

After upgrading from 6.2D to 6.2L on DEC Ultrix, some customers
report a drop in system/application performance. In most cases, the
CPU utilization goes up towards 100% even though there is little
activity and no swapping on the system. Progress Software attributes
this problem to how the 6.2L _progres executable is relinked. For
release 6.2D, _progres was built as a pure executable; for 6.2L it
was built as a demand paging executable.

To resolve the problem, use the PROBUILD utility to rebuild the 6.2L
executable. Before you execute the link script, change the LDOPT
environmant variable and add the -n link symbol to the current
environment variable setting as shown in the following examples.

LDOPT=-Wl,-n;export LDOPT

LDOPT=$LDOPT,-n;export LDOPT

NOTES:

* The other link symbols might differ on certain platforms.

* The -n link symbol might differ on certain platforms. Type "man ld"
to access the man page on ld to find the correct symbol for your
platform.


After you execute the link script, make sure the new executable is a
pure executable. Type "file new_exe" where new_exe is the name of the
new executable. The UNIX file indicates if it is pure or demanding.
For example, if you type "file _progres", the UNIX file displays the
following message.

/usr/dlc/_progres: decstn pure set-uid executable not stripped


This issue is reported with the DEC Ultrix 6.2L port. There is a
similar issue reported, but not verified, on the Arix 825. The
symptoms, after you upgrade to PROGRESS 6.2L, are as follows:

* The UNIX file returns demand paging.
* There is high CPU utilization (not attributed to swapping, high
system load, etc.)

If you observe these symptoms, try to build a pure executable, then
test again.

Progress Software Technical Support Note # 12142