How to calculate the number of vcores on a Linux machine
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
In my Linux machine I have 32 vcores.
And from lscpu, I can see same.
For my CPU, "Thread(s) per core" is 2.
So does it mean that I have actually 64 vcores?
linux rhel cpu lscpu
edited Sep 13 at 8:00
Stephen Kitt
148k22324393
asked Sep 13 at 5:21
yael
2,0391345
add a comment |Â
up vote
1
down vote
favorite
In my Linux machine I have 32 vcores.
And from lscpu, I can see same.
For my CPU, "Thread(s) per core" is 2.
So does it mean that I have actually 64 vcores?
linux rhel cpu lscpu
edited Sep 13 at 8:00
Stephen Kitt
148k22324393
asked Sep 13 at 5:21
yael
2,0391345
What meaning ofvcoreare you using (voltage-core, us used by the top 10 in my google search. Or something else)?
– ctrl-alt-delor
Sep 13 at 8:42
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
In my Linux machine I have 32 vcores.
And from lscpu, I can see same.
For my CPU, "Thread(s) per core" is 2.
So does it mean that I have actually 64 vcores?
linux rhel cpu lscpu
edited Sep 13 at 8:00
Stephen Kitt
148k22324393
asked Sep 13 at 5:21
yael
2,0391345
In my Linux machine I have 32 vcores.
And from lscpu, I can see same.
For my CPU, "Thread(s) per core" is 2.
So does it mean that I have actually 64 vcores?
linux rhel cpu lscpu
linux rhel cpu lscpu
edited Sep 13 at 8:00
Stephen Kitt
148k22324393
asked Sep 13 at 5:21
yael
2,0391345
edited Sep 13 at 8:00
Stephen Kitt
148k22324393
asked Sep 13 at 5:21
yael
2,0391345
edited Sep 13 at 8:00
Stephen Kitt
148k22324393
edited Sep 13 at 8:00
Stephen Kitt
148k22324393
edited Sep 13 at 8:00
Stephen Kitt
148k22324393
148k22324393
asked Sep 13 at 5:21
yael
2,0391345
asked Sep 13 at 5:21
yael
2,0391345
asked Sep 13 at 5:21
yael
2,0391345
2,0391345
What meaning ofvcoreare you using (voltage-core, us used by the top 10 in my google search. Or something else)?
– ctrl-alt-delor
Sep 13 at 8:42
add a comment |Â
What meaning ofvcoreare you using (voltage-core, us used by the top 10 in my google search. Or something else)?
– ctrl-alt-delor
Sep 13 at 8:42
What meaning of
vcore are you using (voltage-core, us used by the top 10 in my google search. Or something else)?– ctrl-alt-delor
Sep 13 at 8:42
What meaning of
vcore are you using (voltage-core, us used by the top 10 in my google search. Or something else)?– ctrl-alt-delor
Sep 13 at 8:42
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
4
down vote
accepted
In the lscpu output, the “CPU(s)†line gives the total number of logical CPUs (aka threads). If it’s run inside a VM, that’s the number of virtual cores assigned to the VM, in your case 32.
The other information provided by lscpu gives more detail, and should end up matching the number of logical CPUs: “Thread(s) per core†× “Core(s) per socket†× “Socket(s)â€Â. The characteristics of the physical CPUs in the host don’t have much bearing on the characteristics of the virtual CPUs inside the VM, and they don’t add to the allocations — if your host CPU has two threads per core, that doesn’t multiply the assigned cores inside the VM.
answered Sep 13 at 6:43
Stephen Kitt
148k22324393
add a comment |Â
up vote
1
down vote
If you have 32 CPU Cores assigned to your Linux machine and each core have 2 threads then you would be having 64 Threads but not 64 cores.
Generally one core can run only thread at a time but these days most of the CPU supports hyper-threading concept where CPU finds idle stages of current thread pipeline to process another to define better multi processing.
But If your Linux machine is virtual then your VM will show logical threads instead of cores in your machine.
answered Sep 13 at 5:40
rɑËÂdʒɑ
2,41972551
No, if you assign a given number of virtual cores to a VM, then you get that many logical CPUs, only.
– Stephen Kitt
Sep 13 at 8:00
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
accepted
In the lscpu output, the “CPU(s)†line gives the total number of logical CPUs (aka threads). If it’s run inside a VM, that’s the number of virtual cores assigned to the VM, in your case 32.
The other information provided by lscpu gives more detail, and should end up matching the number of logical CPUs: “Thread(s) per core†× “Core(s) per socket†× “Socket(s)â€Â. The characteristics of the physical CPUs in the host don’t have much bearing on the characteristics of the virtual CPUs inside the VM, and they don’t add to the allocations — if your host CPU has two threads per core, that doesn’t multiply the assigned cores inside the VM.
answered Sep 13 at 6:43
Stephen Kitt
148k22324393
add a comment |Â
up vote
4
down vote
accepted
In the lscpu output, the “CPU(s)†line gives the total number of logical CPUs (aka threads). If it’s run inside a VM, that’s the number of virtual cores assigned to the VM, in your case 32.
The other information provided by lscpu gives more detail, and should end up matching the number of logical CPUs: “Thread(s) per core†× “Core(s) per socket†× “Socket(s)â€Â. The characteristics of the physical CPUs in the host don’t have much bearing on the characteristics of the virtual CPUs inside the VM, and they don’t add to the allocations — if your host CPU has two threads per core, that doesn’t multiply the assigned cores inside the VM.
answered Sep 13 at 6:43
Stephen Kitt
148k22324393
add a comment |Â
up vote
4
down vote
accepted
up vote
4
down vote
accepted
In the lscpu output, the “CPU(s)†line gives the total number of logical CPUs (aka threads). If it’s run inside a VM, that’s the number of virtual cores assigned to the VM, in your case 32.
The other information provided by lscpu gives more detail, and should end up matching the number of logical CPUs: “Thread(s) per core†× “Core(s) per socket†× “Socket(s)â€Â. The characteristics of the physical CPUs in the host don’t have much bearing on the characteristics of the virtual CPUs inside the VM, and they don’t add to the allocations — if your host CPU has two threads per core, that doesn’t multiply the assigned cores inside the VM.
answered Sep 13 at 6:43
Stephen Kitt
148k22324393
In the lscpu output, the “CPU(s)†line gives the total number of logical CPUs (aka threads). If it’s run inside a VM, that’s the number of virtual cores assigned to the VM, in your case 32.
The other information provided by lscpu gives more detail, and should end up matching the number of logical CPUs: “Thread(s) per core†× “Core(s) per socket†× “Socket(s)â€Â. The characteristics of the physical CPUs in the host don’t have much bearing on the characteristics of the virtual CPUs inside the VM, and they don’t add to the allocations — if your host CPU has two threads per core, that doesn’t multiply the assigned cores inside the VM.
answered Sep 13 at 6:43
Stephen Kitt
148k22324393
answered Sep 13 at 6:43
Stephen Kitt
148k22324393
answered Sep 13 at 6:43
Stephen Kitt
148k22324393
answered Sep 13 at 6:43
Stephen Kitt
148k22324393
148k22324393
add a comment |Â
add a comment |Â
up vote
1
down vote
If you have 32 CPU Cores assigned to your Linux machine and each core have 2 threads then you would be having 64 Threads but not 64 cores.
Generally one core can run only thread at a time but these days most of the CPU supports hyper-threading concept where CPU finds idle stages of current thread pipeline to process another to define better multi processing.
But If your Linux machine is virtual then your VM will show logical threads instead of cores in your machine.
answered Sep 13 at 5:40
rɑËÂdʒɑ
2,41972551
No, if you assign a given number of virtual cores to a VM, then you get that many logical CPUs, only.
– Stephen Kitt
Sep 13 at 8:00
add a comment |Â
up vote
1
down vote
If you have 32 CPU Cores assigned to your Linux machine and each core have 2 threads then you would be having 64 Threads but not 64 cores.
Generally one core can run only thread at a time but these days most of the CPU supports hyper-threading concept where CPU finds idle stages of current thread pipeline to process another to define better multi processing.
But If your Linux machine is virtual then your VM will show logical threads instead of cores in your machine.
answered Sep 13 at 5:40
rɑËÂdʒɑ
2,41972551
No, if you assign a given number of virtual cores to a VM, then you get that many logical CPUs, only.
– Stephen Kitt
Sep 13 at 8:00
add a comment |Â
up vote
1
down vote
up vote
1
down vote
If you have 32 CPU Cores assigned to your Linux machine and each core have 2 threads then you would be having 64 Threads but not 64 cores.
Generally one core can run only thread at a time but these days most of the CPU supports hyper-threading concept where CPU finds idle stages of current thread pipeline to process another to define better multi processing.
But If your Linux machine is virtual then your VM will show logical threads instead of cores in your machine.
answered Sep 13 at 5:40
rɑËÂdʒɑ
2,41972551
If you have 32 CPU Cores assigned to your Linux machine and each core have 2 threads then you would be having 64 Threads but not 64 cores.
Generally one core can run only thread at a time but these days most of the CPU supports hyper-threading concept where CPU finds idle stages of current thread pipeline to process another to define better multi processing.
But If your Linux machine is virtual then your VM will show logical threads instead of cores in your machine.
answered Sep 13 at 5:40
rɑËÂdʒɑ
2,41972551
edited Sep 13 at 11:17
answered Sep 13 at 5:40
rɑËÂdʒɑ
2,41972551
answered Sep 13 at 5:40
rɑËÂdʒɑ
2,41972551
answered Sep 13 at 5:40
rɑËÂdʒɑ
2,41972551
2,41972551
No, if you assign a given number of virtual cores to a VM, then you get that many logical CPUs, only.
– Stephen Kitt
Sep 13 at 8:00
add a comment |Â
No, if you assign a given number of virtual cores to a VM, then you get that many logical CPUs, only.
– Stephen Kitt
Sep 13 at 8:00
No, if you assign a given number of virtual cores to a VM, then you get that many logical CPUs, only.
– Stephen Kitt
Sep 13 at 8:00
No, if you assign a given number of virtual cores to a VM, then you get that many logical CPUs, only.
– Stephen Kitt
Sep 13 at 8:00
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f468703%2fhow-to-calculate-the-number-of-vcores-on-a-linux-machine%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
What meaning of
vcoreare you using (voltage-core, us used by the top 10 in my google search. Or something else)?– ctrl-alt-delor
Sep 13 at 8:42