Kbase 11430: NLM Resource Utilization is High: 80-90%: Why and How to Fix
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/08/2003 |
|
Status: Technically Reviewed
GOAL:
Why is the resource utilization very high for Progress on Novell?
FACT(s) (Environment):
Novell NetWare
FIX:
If you use Progress Version 6.x _mprosrv or _mprotli -N spx at startup, the Novell monitor indicates a high resource useage. This is normal.
Progress uses the processor as long as no other process is using it. Progress sits on the processor at the lowest of priority. As soon as another process requests use of the CPU, Progress releases the processor and there is no performance degradation.
Starting with Version 6.2M15 of the NLM product, Progress shipped only the _mprotli.nlm with the Progress product. With this release, Progress ceased support of _mprosrv.nlm and use of the _mprotli -N spx startup.
Progress requires that you start your NLM server with the _mprotli -N tli startup. This uses Novell's Transport Layer Interface (TLI). This provides NLM support t both TCP/IP and SPX clients (if desired). In addition, the startup gives you a proper useage reading on the Novell monitor.
Please refer to the README.PRO that is shipped with the NLM product for more information on _mprotli -N tli.
NOTE: Progress Version 7.x NLM uses _mprosrv with -N TLI for both SPX and TCP. Starting with Version 7.3E, Progress supports -tcponly but -N still remains TLI.