running CPU cores are less  [Solved]

Help with the version of MX KDE officially released by the Development Team.
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Post Reply
Message
Author
3357
Posts: 97
Joined: Thu Jul 29, 2021 6:03 pm

running CPU cores are less

#1 Post by 3357 »

I have noticed that only two cores are used
as in this snapshot
Image
while the system is quad core

Code: Select all

[code]
System:
  Kernel: 5.10.0-15-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-15-amd64 
  root=UUID=<filter> ro quiet splash 
  Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
  Distro: MX-21.1_KDE_x64 Wildflower April 9  2022 
  base: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Desktop System: LENOVO product: 10A8A0NKAU v: ThinkCentre M93p 
  serial: <filter> 
  Mobo: LENOVO model: SHARKBAY v: SDK0E50510 PRO serial: <filter> 
  BIOS: LENOVO v: FBKT89AUS date: 06/06/2014 
CPU:
  Info: Quad Core model: Intel Core i7-4770 bits: 64 type: MT MCP 
  arch: Haswell family: 6 model-id: 3C (60) stepping: 3 microcode: 28 
  cache: L2: 8 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 54275 
  Speed: 1341 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 1341 
  2: 2304 3: 2572 4: 3660 5: 2289 6: 2224 7: 2159 8: 2511 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, 
  SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, 
  STIBP: conditional, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA GF108 [GeForce GT 430] vendor: Gigabyte 
  driver: nouveau v: kernel bus-ID: 04:00.0 chip-ID: 10de:0de1 
  class-ID: 0300 
  Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: 
  loaded: modesetting unloaded: fbdev,vesa display-ID: :0 screens: 1 
  Screen-1: 0 s-res: 1360x768 s-dpi: 96 s-size: 359x203mm (14.1x8.0") 
  s-diag: 412mm (16.2") 
  Monitor-1: VGA-1 res: 1360x768 hz: 60 dpi: 22 
  size: 1600x900mm (63.0x35.4") diag: 1836mm (72.3") 
  OpenGL: renderer: NVC1 v: 4.3 Mesa 21.2.5 direct render: Yes 
Audio:
  Device-1: Intel 8 Series/C220 Series High Definition Audio 
  vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 
  chip-ID: 8086:8c20 class-ID: 0403 
  Device-2: NVIDIA GF108 High Definition Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus-ID: 04:00.1 chip-ID: 10de:0bea 
  class-ID: 0403 
  Sound Server-1: ALSA v: k5.10.0-15-amd64 running: yes 
  Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:
  Device-1: Intel Ethernet I217-LM vendor: Lenovo driver: e1000e 
  v: kernel port: f040 bus-ID: 00:19.0 chip-ID: 8086:153a class-ID: 0200 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 2.73 TiB used: 1.11 TiB (40.5%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital 
  model: WD10EARS-00Y5B1 size: 931.51 GiB block-size: physical: 512 B 
  logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 0A80 
  scheme: MBR 
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Western Digital 
  model: WD10 01FALS-00E8B0 size: 931.51 GiB block-size: physical: 4096 B 
  logical: 512 B type: N/A serial: <filter> rev: 8102 scheme: MBR 
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Seagate model: M3 
  size: 931.51 GiB block-size: physical: 4096 B logical: 512 B type: N/A 
  serial: <filter> rev: 9300 scheme: MBR 
Partition:
  ID-1: / raw-size: 186.26 GiB size: 182.28 GiB (97.86%) 
  used: 65.54 GiB (36.0%) fs: ext4 dev: /dev/sda4 maj-min: 8:4 
Swap:
  Alert: No swap data was found. 
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 76.0 C 
  Fan Speeds (RPM): N/A 
Repos:
  Packages: 2394 note: see --pkg apt: 2385 lib: 1305 flatpak: 9 
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://deb.debian.org/debian bullseye main contrib non-free
  2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb http://mirror.datamossa.io/mxlinux/mx/repo/ bullseye main non-free
  2: deb http://mirror.datamossa.io/mxlinux/mx/repo/ bullseye ahs
Info:
  Processes: 257 Uptime: 8h 30m wakeups: 1 Memory: 7.7 GiB 
  used: 3.79 GiB (49.2%) Init: SysVinit v: 2.96 runlevel: 5 default: 5 
  tool: systemctl Compilers: gcc: 10.2.1 alt: 10 Shell: bash 
  default: Bash v: 5.1.4 running-in: quick-system-info-mx inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)
[/code]
You do not have the required permissions to view the files attached to this post.

User avatar
Adrian
Developer
Posts: 8270
Joined: Wed Jul 12, 2006 1:42 am

Re: running CPU cores are less

#2 Post by Adrian »

You actually have 8 threads (4 cores x 2 hyperthreads)
1: 1341 2: 2304 3: 2572 4: 3660 5: 2289 6: 2224 7: 2159 8: 2511
I think all are used but whatever you are using to display that info (conky?) doesn't display the full info, there might be a config file where you can specify how many cores you want to see.
How many cores do you see in htop? (You can install something like "stress" and run it with different --cpu loads, like "stress --cpu 4" or "stress --cpu 8")

Or if you don't want to install "stress", here's a simple way to test, run:

Code: Select all

yes > /dev/null &
Note that running the above command once only imposes 100% load on a single core. If you have multiple, for example, four cores, run the command four times to exhaust all the CPU power:

$ yes > /dev/null &
$ yes > /dev/null &
$ yes > /dev/null &
$ yes > /dev/null &

User avatar
siamhie
Posts: 1619
Joined: Fri Aug 20, 2021 5:45 pm

Re: running CPU cores are less

#3 Post by siamhie »

What's the name of that conky?
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.

3357
Posts: 97
Joined: Thu Jul 29, 2021 6:03 pm

Re: running CPU cores are less

#4 Post by 3357 »

I ran the following
$ stress --cpu 3 --timeout 10s
stress: info: [18477] dispatching hogs: 3 cpu, 0 io, 0 vm, 0 hdd
stress: info: [18477] successful run completed in 10s
nn@mxkde:~
$ stress --cpu 4 --timeout 10s
stress: info: [18483] dispatching hogs: 4 cpu, 0 io, 0 vm, 0 hdd
stress: info: [18483] successful run completed in 10s

Does this mean the 4 are running?

User avatar
wdscharff
Posts: 1000
Joined: Mon Feb 24, 2020 2:07 am

Re: running CPU cores are less  [Solved]

#5 Post by wdscharff »

The problem with Conky is that it only shows what has been configured. For example, in order for it to display all 12cores/24threads, I had to start an excessive copy&paste action (and adjust the assignments).
The starting point for this was a conky that displayed 8 cores/threads (and none more!).
Have fun adapting ;-}

So you don't have a problem with the load of your threads, but only a (typical) display problem of Conky.

Translated with www.DeepL.com/Translator (free version)
Desktop AMD Ryzen 9 3900x, 32GB Ram // SSD ... enough
Laptop Acer Core I5-7300HQ, 8GB Ram / SSD intern 256GB&2TB
mx-fluxbox, what else?

In nature there are neither rewards nor punishments.
There are consequences.


my wallpaper gallery

3357
Posts: 97
Joined: Thu Jul 29, 2021 6:03 pm

Re: running CPU cores are less

#6 Post by 3357 »

yes
thanks
all good

User avatar
Adrian
Developer
Posts: 8270
Joined: Wed Jul 12, 2006 1:42 am

Re: running CPU cores are less

#7 Post by Adrian »

Does this mean the 4 are running?
No,

Code: Select all

stress --cpu 150
stress: info: [27875] dispatching hogs: 150 cpu, 0 io, 0 vm, 0 hdd
The point was to run htop, or top (but htop is more clear in how it displays info) at the same time to show you all the cores being engaged while you are running the stress program.

Post Reply

Return to “MX KDE Official Release”