Subject | Firebird in VMWare |
---|---|
Author | Alan McDonald |
Post date | 2009-05-21T03:55:10Z |
I have a client who wishes to move all dataservers into a virtual
environment.
Eventually my superserver installations are intended to be domiciled on
DELL R900 4 core servers running VMWare ESX3.5 (c/w Virtual Centre) and
Windows Server 2008
It's also intended for them to use VMotion to switch service from one
virtual environment to another on-the-fly.
My question.
I understand VMware can nominate single or multi core use. Not sure if a
declaration of single core use in VMWare is transparent to Firebird since
the VMWare may still broker requests for CPU time to any of the 4 cores
depending on load.
Does anyone have experience here as to whether I can stick with SuperServer
(which is what it is at this time) or if I need to switch to Classic to make
best use of the FB service. If the FB super sees thru the VMware core
switching, this may be to the detriment of performance.
thanks
regards
Alan McDonald
environment.
Eventually my superserver installations are intended to be domiciled on
DELL R900 4 core servers running VMWare ESX3.5 (c/w Virtual Centre) and
Windows Server 2008
It's also intended for them to use VMotion to switch service from one
virtual environment to another on-the-fly.
My question.
I understand VMware can nominate single or multi core use. Not sure if a
declaration of single core use in VMWare is transparent to Firebird since
the VMWare may still broker requests for CPU time to any of the 4 cores
depending on load.
Does anyone have experience here as to whether I can stick with SuperServer
(which is what it is at this time) or if I need to switch to Classic to make
best use of the FB service. If the FB super sees thru the VMware core
switching, this may be to the detriment of performance.
thanks
regards
Alan McDonald