Witaj na Forum Linuxiarzy
Zanim zalogujesz się, by pisać na naszym forum, zapoznaj się z kilkoma zasadami savoir-vivre'u w dziale Administracja.
Wiadomości z problemami zamieszczone w wątku "Przywitaj się" oraz wszelkie reklamy na naszym forum będą usuwane.

Wysokie użycie CPU na Sparky Xfce

Zaczęty przez lami07, Grudzień 06, 2017, 01:04:24 PM

Poprzedni wątek - Następny wątek

lami07

W dziale sparky forum są dwa tematy odnośnie wysokiego użycia CPU na sparky Xfce, które jak przypuszczam są tożsame z sytuacją, na którą ja się nadziałem. Domyślna dla sparky xfce konfiguracja pulpitu zawiera na panelu dwa aplety. Aplet regulacji głośności (xfce4-pulseaudio-plugin) i aplet daty/czasu (xfc4-datetime-plugin). Oba bezpośrednio lub pośrednio powodują prace procesora na najwyższych "obrotach".

Tak przedstawiał się u mnie raport cpufreq-info na świeżej instalacji z obydwoma apletami na panelu :
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 2.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 2.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.10 GHz.
analyzing CPU 1:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 2.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 2.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.10 GHz.
analyzing CPU 2:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 2.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 2.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.10 GHz.
analyzing CPU 3:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 2.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 2.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.10 GHz.


Jak widać na komputerze gdzie skalowaniem częstotliwości zajmuje się intel_pstate, wszystkie rdzenie pracują "pełną parą" bez przerwy. 70 stopni na procku, bez żadnego dodatkowego obciążenia, tylko uruchomiony Sparky. Lapek żony ma starszej generacji procek, sterowany przez acpi-cpufreq. Tam sytuacja wyglądała trochę lepiej. Tylko jeden rdzeń pracował na maksa, reszta skakała pomiędzy częstotliwością minimalną i maksymalną.

Tak wygląda sprawa po usunięciu apletów z panelu:
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 2.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 2.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 950 MHz.
analyzing CPU 1:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 2.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 2.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 798 MHz.
analyzing CPU 2:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 2.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 2.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 798 MHz.
analyzing CPU 3:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 2.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 2.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 812 MHz.


W gałęzi Sparky rolling problem już nie obowiązuje, wystarczy zaktualizować system (sudo apt update && sudo apt full-upgrade). Niestety w gałęzi Sparky stable nadal jest.

Jeśli ktoś chce zweryfikować to o czym tu pisałem wystarczy, że odpali sparky xfce z liveusb.

Pozdrawiam. Szymon.

IRC - #linuxiarze.pl w sieci [url="//libera.chat"]libera.chat[/url]
Matrix - #linuxiarze.pl w sieci [url="//matrix.org"]matrix.org[/url]

Zobacz najnowsze wiadomości na forum