Sun HPC ClusterTools 3.0 Administrator's Guide: With LSF

Applications and I/O Processes, Colocate or Run Separately?

If you plan to configure only a subset of the nodes on a cluster as PFS I/O servers, you will have the option of either colocating applications and I/O daemons on the same PFS I/O servers or segregating them onto separate nodes. If, however, you configure all the nodes in a cluster as PFS I/O servers, you will of necessity colocate applications and PFS I/O daemons.

Guidelines for making this choice are provided below.

Conditions That Favor Colocating

Each of the following conditions favors colocating applications with PFS I/O daemons.

When these conditions exist in combination, the network is more likely to be a performance-limiting resource than the relatively more powerful nodes. Therefore, it becomes advantageous to locate applications on the PFS I/O servers to decrease the amount of data that must be sent across the network.

Conditions That Favor Separating Applications and IODs

You should avoid running applications on I/O server nodes when some or all of the following conditions exist.

In this case, the competition for memory, bus bandwidth, and CPU cycles may offset any performance advantages local storage would provide.

Effect of Cluster Size

By itself, the size of a cluster (number of nodes) does not favor either colocating or not colocating applications and PFS I/O daemons. Larger clusters do, however, attenuate the benefits of colocating. This is because the amount by which colocating reduces network traffic can be expressed as

    Tc = Ts - Ts/N

where Tc is the level of network traffic using colocating, Ts is the level of network traffic without colocating, and N is the number of nodes in the cluster. In other words, colocating reduces network traffic by 1/number-of-nodes. The more nodes there are in the cluster, the smaller the effect of colocating.