About branch warming
With branch warming enabled, the server-side appliance keeps track of data segments created while Client Accelerator users are in a SteelHead-enabled branch office. When the user leaves the branch office, the Client Accelerator endpoint software provides warm performance. Enabled by default.
Other endpoints at a branch office benefit from branch warming as well, because data transferred by one endpoint at a branch also populates the branch SteelHead’s data store. Performance improves with all endpoints at the branch because they receive warm performance for that data.
These requirements must be met for branch warming to work:
• Enable latency-based location awareness and branch warming on the Client Accelerator Controller.
• Enable branch warming and enhanced autodiscovery on the client-side and server-side SteelHeads.
• Client-side and server-side SteelHeads must be deployed in-path.
Branch warming doesn’t improve performance for SSL connections, out-of-path with fixed-target rules deployments, and Client Accelerator endpoints that communicate with multiple server-side appliances in different scenarios. For example, if a Client Accelerator home user peers with one server-side SteelHead after logging in through a VPN network and peers with a different server-side SteelHead after logging in from the branch office, branch warming doesn’t improve performance.