Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Weird issue with multi socket CPUs

See original GitHub issue

Describe the bug When running si.cpu() on a multi-socket server the results are incorrect.

To Reproduce

Get multi-socket server
Run command
Profit?

Current Output

{ manufacturer: 'Intel®',
  brand: 'Xeon® X5650',
  vendor: 'GenuineIntel',
  family: '6',
  model: '44',
  stepping: '2',
  revision: '',
  voltage: '',
  speed: '2.67',
  speedmin: '',
  speedmax: '',
  cores: 24,
  physicalCores: 3,
  processors: 2,
  socket: 'LGA1366',
  cache: { l1d: 393216, l1i: 393216, l2: 3, l3: 24 } }

Expected behavior I think this is the correct result. The server is using 2x 6 core CPUs with 2 threads per core.

{ manufacturer: 'Intel®',
  brand: 'Xeon® X5650',
  vendor: 'GenuineIntel',
  family: '6',
  model: '44',
  stepping: '2',
  revision: '',
  voltage: '',
  speed: '2.67',
  speedmin: '',
  speedmax: '',
  cores: 24,
  physicalCores: 12,
  processors: 2,
  socket: 'LGA1366',
  cache: { l1d: 393216, l1i: 393216, l2: 3, l3: 24 } }

Environment (please complete the following information):

systeminformation package version: latest
OS: macOS and Unraid
Hardware: MacBook Pro 2010 and Dell R710

Additional context For reference the same version of si works perfect on my single-socket Macbook.

{
  manufacturer: 'Intel®',
  brand: 'Core™ i5 M 520',
  vendor: 'GenuineIntel',
  family: '6',
  model: '37',
  stepping: '5',
  revision: '',
  voltage: '',
  speed: '2.40',
  speedmin: '2.40',
  speedmax: '2.40',
  cores: 4,
  physicalCores: 2,
  processors: 1,
  socket: '',
  cache: { l1d: 32768, l1i: 32768, l2: 262144, l3: 3145728 }

Issue Analytics

State:
Created 4 years ago
Comments:8 (8 by maintainers)

Top GitHub Comments

1reaction

sebhildebrandtcommented, Oct 14, 2019

@OmgImAlexis - thank you for testing! New version published on npm v4.14.12

1reaction

sebhildebrandtcommented, Oct 13, 2019

@OmgImAlexis I changed the code now (not yet released on npm). Can you test it on your side? you only need to grab lib/cpu.js from github and replace your existing one. If this returns good results, I will publish this on npm. Thank you in advance!!