Hacker News Reader

Comment by drKarl | Hacker News Reader

Just rebooted and made cat /proc/cpuinfo and the and its 2.27Ghz, so the last of the 8 CPUs is

processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU L5520 @ 2.27GHz stepping : 5 microcode : 0x11 cpu MHz : 2266.746 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 1 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu de tsc msr pae cx8 cmov pat clflush mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc pni ssse3 sse4_1 sse4_2 popcnt hypervisor bogomips : 4533.49 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management:

View on HN

I just rebooted one of my Linodes, and I got this:

    processor       : 7
    vendor_id       : GenuineIntel
    cpu family      : 6
    model           : 45
    model name      : Intel(R) Xeon(R) CPU E5-2650L 0 @ 1.80GHz
    stepping        : 7
    microcode       : 0x70a
    cpu MHz         : 1800.059
    cache size      : 20480 KB
    physical id     : 0
    siblings        : 8
    core id         : 0
    cpu cores       : 1
    apicid          : 0
    initial apicid  : 13
    fdiv_bug        : no
    hlt_bug         : no
    f00f_bug        : no
    coma_bug        : no
    fpu             : yes
    fpu_exception   : yes
    cpuid level     : 13
    wp              : yes
    flags           : fpu de tsc msr pae cx8 cmov pat clflush mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc pni pclmulqdq ssse3 sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes hypervisor ida arat epb pln pts dtherm
    bogomips        : 3600.11
    clflush size    : 64
    cache_alignment : 64
    address sizes   : 46 bits physical, 48 bits virtual
    power management:

Edit: I should perhaps mention that this is a 512MB Linode, on the off chance that it makes a difference.

I rebooted mine as well and got @ 2.27 GHz, so I guess that they probably haven't gotten to your server yet.

That is the old 4 core cpu they have been using. We will probably have to wait some weeks before this all takes effect.

Pretty sure just reading the post answers this, "Linodes will start landing on NextGen hardware in the next week or so".

The post is a bit confusing, though, because well before you get to the line that you quoted, the article states:

"And we’re upgrading all Linodes to 8 cores! Right now. As in all you need to do is reboot to double the computing power of your Linode. By the time the host refresh is completed the average Linode will be running on hardware that is less than 1 year old."

I, for one, thought that it was ready now after reading that. In fact, from the comments, it's clear that for some customers, this is in fact ready:

"BizzarTech: Rebooted my 1024 and moar cores!!! Thank you!!"

No, the move to new hardware and increase in the number of available cores is separate. If you reboot right now you'll get access to more of the 'cores' on the host system (though I suspect they're really just "threads" in Intel terminology). But you're still running on the older L5520 hardware.

I rebooted and confirmed; indeed the older L5520 is still the processor being used on my particular linode:

<snip>

    processor       : 7
    vendor_id       : GenuineIntel
    cpu family      : 6
    model           : 26
    model name      : Intel(R) Xeon(R) CPU           L5520  @ 2.27GHz
    stepping        : 5
    microcode       : 0x11
    cpu MHz         : 2266.746
    cache size      : 8192 KB
    physical id     : 0
    siblings        : 8

</snip>

This is from a plan that is less than a week old:

  processor	: 7
  vendor_id	: GenuineIntel
  cpu family	: 6
  model		: 44
  model name	: Intel(R) Xeon(R) CPU           L5630  @ 2.13GHz
  stepping	: 2
  microcode	: 0x15
  cpu MHz		: 2133.460
  cache size	: 12288 KB
  physical id	: 0
  siblings	: 8

Reply on news.ycombinator.com