(09-27-2020, 09:36 PM)deanhills Wrote: Sounds like a great plan @fChk.
For now I've added @phoenixwolf's vCPU number to the VPS 14 plan.
Next I'll start with VPS 1 and work my way up from there.
@
deanhills
I noted that you've used the 'Number of CPU Cores' instead of simply 'vCPU'; that's inaccurate.
Virtualization guests (be it under QEMU/KVM or Hyper-V) don't have CPU Cores but are assigned virtual CPU (ie vCPU) --also referred to as 'logical CPUs' at runtime by the adhoc hypervisor, which are simple POSIX threads in the host and that get scheduled by the KVM host scheduler.
Thus if we gave 1 vCPU to our VM then it will have 1 POSIX thread to run in, if 2 then 2 threads etc..
The number of vCPUs is set when that VM(/VPS) is built and it's defined by the topology that the VM creator has set for it.
In the case of VPS 9, it's:
root@kvm-Post2Host-Phoenix:~# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 46 bits physical, 48 bits virtual
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 2
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 63
Model name: Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
Stepping: 2
CPU MHz: 2399.996
BogoMIPS: 4799.99
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
NUMA node0 CPU(s): 0,1
Flags: ..........................
Thus the topology is:
> Sockets: 2
> Cores: 1
> Treads: 1
Which means that we have 2 * 1 * 1 = 2 vCPUs.
Now, if you can run the lscpu command inside VPS 14 and post it here that would be great, if not, we'll just have to wait for the next VPS holder to tell us what he's got.
The thing is that if we take what @
phoenixwolf above is saying at face value (ie 'it will have 4 CPU Cores. Running @ 3.5 GHz'), that means VPS 14 has effectively 8 vCPUs not 4!
> Sockets: 1
> Cores: 4
> Treads: 2
=> 1 * 4 * 2 = 8 vCPUs
... Hence why I asked about the topology.
Anyway, I think I will pass on VPS 14 given the HDD storage...
