High Level Considerations for Sizing Virtual Appliances
Keep the following in mind as you determine how to best size the Virtual Appliance for your environment.
gateway83
Keep the following in mind as you determine how to best size the Virtual Appliance for your environment.
- Size of message traffic: Larger messages require more memory. Typically, 4GB of memory is sufficient for reasonable message traffic up to 1 MB messages. If you expect your messages to be larger, 8GB will allow you to handle up to 100MB messages.
- May be advantageous to set up different Gateway nodes for different message sizes, and size the images differently.
- Expected load: Consistent very high load requires both CPUs and memory, regardless of message size . You may want to consider reserving resources for the Gateway.
- Policy makeup: Using CPU-heavy assertions require CPU resources. It might be advantageous to reserve a CPU for the Gateway. Assertions that are CPU-heavy typically deal with XSLT, message encryption and signature validation, schema validations.
- Abnormal message behavior: Variables such as burst request traffic or high back-end latencies may require other considerations, especially when sizing memory for the Virtual Appliance.
Adding more resources does not always produce greater performance. For example, allocating too many CPU resources or too much memory to images may actually cause a
decrease
in overall performance. VMware is designed to reclaim resources that it considers idle and this reclaiming/reallocating cycle impacts performance.