CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.3+)

information about the status and use of communication lines, processes, and related resources.
NonStop CORBA Performance Tuning
Performance tuning of the runtime environment of the NonStop CORBA system is primarily a matter of deciding
on the number and relationships among Location Service Daemon (LSD), Comm Server, and TCP/IP processes:
You use PATHCOM to define the number of Comm Servers.1.
You use the Configuration Tool to define the relationships among the LSD, Comm Servers, TCP/IP
processes, remote clients, and application servers.
2.
You can use PATHCOM to locate and resolve a NonStop CORBA system performance problem.3.
You can use the cfgmgt tool and the nsdstart script to configure Parallel Library TCP/IP to increase
capacity.
4.
The use of underlying networking services (X25AM and LAN) by TCP/IP can also affect the performance of the
NonStop CORBA runtime environment. You use SCF to establish and monitor those relationships.
Caution
NonStop CORBA does not use TS/MP to provide automatic load balancing for Comm Servers. Instead, the
relationships among clients and the Comm Servers are fixed by the LSD configuration. Thus, assumptions about
TS/MP load balancing and performance tuning will not always apply to managing the NonStop CORBA runtime
environment.
For example, a bottleneck could occur in a Comm Server even if other servers in the pool were idle; in this case,
you would improve performance by using the Configuration Tool to modify the assignment of clients to Comm
Servers rather than by using PATHCOM to add Comm Server processes.
Often a perceived problem with NonStop CORBA system performance is actually the result of application design
and configuration, such as the use of requests to stateful objects and the locations and design of objects that
frequently exchange data.
NonStop CORBA Troubleshooting
The most common problems preventing successful operation of the NonStop CORBA system are the following:
Configuration errors●
Inconsistencies in configuration between the NonStop CORBA system and another system with which it
must communicate
●
Other interoperability problems, such as differing implementations of a CORBA-defined feature on
different platforms
●
Transient networking failures●
Resolving a problem that arises in the interaction between the NonStop CORBA system and some other ORB
typically requires collaboration with the remote administrator. In this case your best tool is a full, up-to-date set of
the NonStop CORBA and SCF configuration files. However, several automated tools can also help you
troubleshoot your local NonStop CORBA system: