Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Info about core and core speed
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Info about core and core speed

NANONANO Member
edited June 2017 in Help

Hello!

How can I know how many cores has my VPS and the speed of them?

I have SolusVM panel but cant find that info there... so I think I have to dig into command line... ¿?

Comments

  • racksxracksx Member

    cat /proc/cpuinfo

    Thanked by 2NANO Aidan
  • saibalsaibal Member

    lshw -class processor

    Thanked by 1NANO
  • @NANO said:
    Hello!

    How can I know how many cores has my VPS and the speed of them?

    I have SolusVM panel but cant find that info there... so I think I have to dig into command line... ¿?

    As specified you can use this command to get information

    cat /proc/cpuinfo

    But with KVM virtualization you will not get information about the CPU being used in host node.

    For that you will have to ask your provider.

  • daffydaffy Member

    @cyberpersons said:

    But with KVM virtualization you will not get information about the CPU being used in host node.

    For that you will have to ask your provider.

    Well, not entirely correct. That depends on the setup of the node.

  • @daffy said:

    @cyberpersons said:

    But with KVM virtualization you will not get information about the CPU being used in host node.

    For that you will have to ask your provider.

    Well, not entirely correct. That depends on the setup of the node.

    Is it possible with solusvm?

  • daffydaffy Member

    @cyberpersons said:

    @daffy said:

    @cyberpersons said:

    But with KVM virtualization you will not get information about the CPU being used in host node.

    For that you will have to ask your provider.

    Well, not entirely correct. That depends on the setup of the node.

    Is it possible with solusvm?

    No idea, idiotic design if it isn't.

  • @daffy said:

    @cyberpersons said:

    @daffy said:

    @cyberpersons said:

    But with KVM virtualization you will not get information about the CPU being used in host node.

    For that you will have to ask your provider.

    Well, not entirely correct. That depends on the setup of the node.

    Is it possible with solusvm?

    No idea, idiotic design if it isn't.

    Alright, well I've worked with proxmox and Guest VM does not show the details of host node.

  • daffydaffy Member

    @cyberpersons said:

    @daffy said:

    @cyberpersons said:

    @daffy said:

    @cyberpersons said:

    But with KVM virtualization you will not get information about the CPU being used in host node.

    For that you will have to ask your provider.

    Well, not entirely correct. That depends on the setup of the node.

    Is it possible with solusvm?

    No idea, idiotic design if it isn't.

    Alright, well I've worked with proxmox and Guest VM does not show the details of host node.

    We do on our Proxmox setup. It's possible to setup from the Proxmox GUI if you have access to that. Not that's it very important, but still...

  • NANONANO Member

    @saibal said:
    lshw -class processor

    lshw -class processor

    *-cpu
    product: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
    vendor: Intel Corp.
    physical id: 1
    bus info: cpu@0
    width: 64 bits
    capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf cpuid_faulting pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc

    This mean that I have just one core or two?

  • FredQcFredQc Member
    edited June 2017

    NANO said: This mean that I have just one core or two?

    Better do cat /proc/cpuinfo and count the cpu cores numbers from 0

    Thanked by 1NANO
  • jarjar Patron Provider, Top Host, Veteran

    @cyberpersons said:

    @daffy said:

    @cyberpersons said:

    But with KVM virtualization you will not get information about the CPU being used in host node.

    For that you will have to ask your provider.

    Well, not entirely correct. That depends on the setup of the node.

    Is it possible with solusvm?

    CPU passthrough is a feature of the virtualization itself and not something solusvm needs to support. However, it does support it. See this to understand how it is set: https://libvirt.org/formatdomain.html#elementsCPU

  • @jarland said:

    @cyberpersons said:

    @daffy said:

    @cyberpersons said:

    But with KVM virtualization you will not get information about the CPU being used in host node.

    For that you will have to ask your provider.

    Well, not entirely correct. That depends on the setup of the node.

    Is it possible with solusvm?

    CPU passthrough is a feature of the virtualization itself and not something solusvm needs to support. However, it does support it. See this to understand how it is set: https://libvirt.org/formatdomain.html#elementsCPU

    Thank you, I will look into this.

  • NANONANO Member

    @FredQc said:
    Better do cat /proc/cpuinfo and count the cpu cores numbers from 0

    processor : 0
    vendor_id : GenuineIntel
    cpu family : 6
    model : 63
    model name : Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
    stepping : 2
    microcode : 54
    cpu MHz : 3501.000
    cache size : 15360 KB
    physical id : 0
    siblings : 12
    core id : 0
    cpu cores : 6
    apicid : 0
    initial apicid : 0
    fpu : yes
    fpu_exception : yes
    cpuid level : 15
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf cpuid_faulting pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc
    bogomips : 6999.41
    clflush size : 64
    cache_alignment : 64
    address sizes : 46 bits physical, 48 bits virtual
    power management:

    This means only one core?!

  • FredQcFredQc Member
    edited June 2017

    NANO said: This means only one core?!

    Looks like it, but that's a nice one. Are you paying for more than one core?

  • qtwrkqtwrk Member

    @NANO said:

    @FredQc said:
    Better do cat /proc/cpuinfo and count the cpu cores numbers from 0

    processor : 0
    vendor_id : GenuineIntel
    cpu family : 6
    model : 63
    model name : Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
    stepping : 2
    microcode : 54
    cpu MHz : 3501.000
    cache size : 15360 KB
    physical id : 0
    siblings : 12
    core id : 0
    cpu cores : 6
    apicid : 0
    initial apicid : 0
    fpu : yes
    fpu_exception : yes
    cpuid level : 15
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf cpuid_faulting pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc
    bogomips : 6999.41
    clflush size : 64
    cache_alignment : 64
    address sizes : 46 bits physical, 48 bits virtual
    power management:

    This means only one core?!

    If I'm reading it correctly, it's 12 cores

  • FredQcFredQc Member

    qtwrk said: If I'm reading it correctly, it's 12 cores

    It's a fucking VPS. I doubt it has "12 cores".

    @NANO Is it OpenVZ ?

  • saibalsaibal Member

    @NANO said: This mean that I have just one core or two?

    Just one. This is the output from my single core Aruba VPS

    lshw -class processor *-cpu product: Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc aperfmperf pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 popcnt aes hypervisor lahf_lm ida arat pln pts dtherm

    @qtwrk said: If I'm reading it correctly, it's 12 cores

    Are those cores from the host node? The E5-1650 has 6 cores (12 threads with H/T)
    http://ark.intel.com/products/64601/Intel-Xeon-Processor-E5-1650-12M-Cache-3_20-GHz-0_0-GTs-Intel-QPI

  • AnthonySmithAnthonySmith Member, Patron Provider

    jarland said: CPU passthrough is a feature of the virtualization itself and not something solusvm needs to support. However, it does support it.

    Sadly however with solusvm if you install from ISO you default to qemu CPU (And IDE disk drivers), so while it supports it you have to manually update each vm (and reboot) on a per VPS basis which is just silly.

    The issue with this is that customers unless they specifically know this and know how solusvm works in detail (why would they) then they get fairly significantly worse performance and it puts a needless load on the host node for emulation.

    I logged an improvement request for it as the support to set the defaults is already present for templates but @OnApp_Terry said that it was by design and rejected the request.

  • qtwrkqtwrk Member

    This line

    siblings : 12 core id : 0 cpu cores : 6

    6 physical core. With HT make it 12...
    At least i think so.

  • Also important to note, however, is that if your provider is overselling their boxes you may not be able to max a core to 100% usage. Or if they're CPU throttling, you may also not be able to reach 100% CPU usage. I'm assuming you want to know the host CPU cores to determine your performance. However the best way to test the performance of your VPS would probably be to test how it performs with the applications you want to run, rather than looking up the CPU model.

  • JunklessJunkless Member
    edited June 2017

    @qtwrk said:
    This line

    siblings : 12.
    core id : 0.
    cpu cores : 6.

    6 physical core. With HT make it 12...
    At least i think so.

    Fixed it for you. The core count is for the processor, not what is allotted to the vps. That's still 1 core.

    Thanked by 1FredQc
  • FredQcFredQc Member

    Fixed it for you. The core count is for the processor, not what is allotted to the vps. That's still 1 core.

    Yeah, with OVZ you will see the hostnode numbers of cores, but with KVM you will see what is really allocated to your VPS...

  • qtwrkqtwrk Member
    edited June 2017

    @FredQc said:

    Fixed it for you. The core count is for the processor, not what is allotted to the vps. That's still 1 core.

    Yeah, with OVZ you will see the hostnode numbers of cores, but with KVM you will see what is really allocated to your VPS...

    oops , just checked it out.
    you are right , sorry , didn't know about this.
    and thanks , new thing learnt

  • NANONANO Member
    edited June 2017

    I was asking because I bought vps with 2 cores and just got one by error, the provider fixed the problem.

    @FredQc said:
    @NANO Is it OpenVZ ?

    Yes, OpenVZ

Sign In or Register to comment.