If testing reveals that your application is disk I/O-bound, and your application does not require failover support (which may be acceptable for very small forms), then you can configure each instance of the Translator to use a local, unshared file system instead of the Shared File Cache. Use a dedicated volume or partition for the Shared File Cache on each virtual server. (Multiple Translator instances on the same virtual server can each use a separate Shared File Cache or they can all share the same Shared File Cache.)
If each virtual server contains only one Translator instance, then there will not be any form of failover support. If one Translator instance fails, the load balancer will transfer the connection to another Translator instance (on a different virtual server) and the user’s data from the original Translator instance will be lost.
If each virtual server contains more than one Translator instance, and Translator instances on a common virtual server share the same Shared File Cache, then limited failover support will be provided. If one Translator instance fails, the load balancer will transfer the connection to another Translator instance. If both Translator instances are on the same virtual server, then the user’s data will be maintained. However, if the Translator instances are on different virtual servers, then the user’s data will be lost.
Parent topic: Setting up and tuning the Shared File Cache