Vertica runs in the following virtualization environment:
Important: Vertica does not support suspending a virtual machine while Vertica is running on it.
VMware version 5.5
The number of virtual machines per host did not exceed the number of physical processors
CPU frequency scaling turned off at the host level and for each virtual machine
VMware parameters for hugepages set at version. 5.5 defaults
Measured by vioperf concurrently on all Vertica nodes When running vioperf, provide the –duration=2min option and start on all nodes concurrently
25 megabytes per second per core of write
20+20 megabytes per second per core of rewrite
40 megabytes per second per core of read
150 seeks per second of latency (SkipRead)
Thick provisioned disk, or pass-through-storage
Dedicated 10G NIC for each Virtual Machine
No oversubscription at the switch layer, verified with vnetperf
Architecture of Sandy Bridge (HP Gen8 or higher)
8 or more virtual cores per virtual machine
vcpuperf time of no more than 12 seconds ( ~= 2.2 GHz clock speed)
Pre-allocate and reserve memory for the VM
4G per virtual core of the virtual machines
HP has tested the configuration above. While other virtualization configurations may have been successfully deployed by customers in development environments, performance of these configurations may vary. If you choose to run Vertica on a different virtualization configuration and experience an issue, the Vertica Support team may ask you to reproduce the issue using the configuration described above, or in a bare-metal environment, to aid in troubleshooting. Depending on the details of the case, the Support team may also ask you to enter a support ticket with your virtualization vendor.
Was this topic helpful?
Thank you for your feedback!
Thank you for your feedback! How can we improve this topic?
Thanks! Your feedback helps to improve this topic for everyone.