If network resources are a bottleneck for your application, overall performance can be improved by isolating intra-cluster traffic from external request traffic. This requires multiple NICs on your server machines, with request traffic coming in on one NIC and intra-cluster traffic using another. Once you have the hardware set up, it is easy to tell the Enterprise Web Platform nodes to use a different interface for the intra-cluster traffic:

./run.sh -c production -b 10.0.0.104 -Djgroups.bind_addr=192.168.100.104

In the above example, the -Djgroups.bind_addr setting tells the the Enterprise Web Platform to run intra-cluster JGroups traffic over the 192.168.100.104 interface. The -b switch specifies that all other traffic should use 10.0.0.104.