On Intel @ 2.6GHZ I would:
- Disable hyperthreading (but not on AMD, only Intel)
- Configure three CPU VPs per core
- Use affinity if there are multiple chips/sockets to limit CPU VP migration off a single socket where practical. Affine other VP types (NET, AIO, etc.) to the other sockets.
- The only exception would be a DSS environment (complex queries, single threaded) where I would do one VP per core across all sockets.
The only problem with VM environments, besides the possibility of sharing resources on the "frame", is that performance is inconsistent making it hard to test and evaluate different configurations. Make many tests with each setup before deciding which is working for you.
------------------------------
Art S. Kagel, President and Principal Consultant
ASK Database Management Corp.
www.askdbmgt.com------------------------------
Original Message:
Sent: Tue May 17, 2022 12:45 PM
From: Eric Vercelletto
Subject: CPU VPs configuration on VMWARE
Hi folks, long time no see, I hope everybody doing well.
I have a question: I have read and tested configuring more than one CPU VP per core on AIX Power VM, using SMT=2 or 1 at the system level. This works pretty well.
I would like to know what is your opinion (with respective real life production experience) to do such a config on a VMWARE/Intel architecture.
The hypervisor will host Xeon Gold procs @2,6Ghz. Preferably no other VM in that system.
Up to how many CPU VPS would you configure per CORE .
- Definitely 1 per core, not more ?
- 2 per core ?
- 3 per core ?
- More ?
Art K has been talking about 1 CPU VP per 'slice' of 700Khz, does this work also with VMWare/Intel ?
Thanks
Eric
Eric Vercelletto
Data Management Architect and Owner / Begooden IT Consulting
KandooERP Founder and CTO
IBM Champion 2013,2014,2015,2016,2017,2018,2019,2020
Tel: +33(0) 298 51 3210
Mob : +33(0)626 52 50 68
skype: begooden-it
Google Hangout: eric.vercelletto@begooden-it.com
Email: eric.vercelletto@begooden-it.com
www : http://www.vercelletto.com
www https://kandooerp.org