NCache 4.4 - Online Documentation

IP Binding

 
By using multiple network interface cards, the network load can be distributed and thus can increase bandwidth throughput. NCache being a network intensive solution, allows the use of dual NIC's and thus network load for cache communication will be distributed on two NICs which will enhance the overall performance.
 
NCache involves two kinds of network communication in a cache cluster.
 
  • Communication between cache server nodes (server-to-server communication).
  • Communication between cache client and cache server (client-to-server communication).
 
Different NIC cards can be configured for each type of network communication in NCache. One NIC will be dedicated for server-to-server communication inside the cache cluster and the second NIC will be reserved only for client-to-server communication. BindToClusterIP will be specified for cluster-wide(server-to-server) communication, and through BindToClientServerIP, NCache can be informed which interface to use for client communication with cache server.
 
In this way, network load for cache communication is distributed on two NICs and resources will be utilized more efficiently, thus increasing the overall performance.
 
NCache can detect all Network Interface Cards (NICs) on a server node and allows the user to choose any of them. Selected NIC will be used by NCache for cluster wide communication. If there are two NICs available on a cache server, then it is highly recommended to use both NICs for these NCache communications. NCache will start utilizing both Network Interface Cards (NICs) on cache servers, once dual NIC interface is configured. Using dual NICs will enhance the overall bandwidth throughput by distributing load on two NICs, thus increasing the performance immensely.
 
Dual NICs can be configured for NCache through NCManager. NCache service config file in installation directory can be manually updated for this purpose.
 
Command line tools provided by NCache communicate with NCache server on BindToClusterIP.
 
 
See Also