Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pironman takes up a whole core #7

Open
Willy65 opened this issue Oct 6, 2024 · 1 comment
Open

Pironman takes up a whole core #7

Willy65 opened this issue Oct 6, 2024 · 1 comment

Comments

@Willy65
Copy link

Willy65 commented Oct 6, 2024

When pironman is started, it consumes 100% CPU time on 1 core.
See output below from top command, after issuing "pironman start" from the commandline (as root):

> ```
> top - 21:33:05 up 43 min,  4 users,  load average: 1.77, 0.87, 0.44
> Tasks: 194 total,   2 running, 192 sleeping,   0 stopped,   0 zombie
> %Cpu0  :  0.0 us,  0.3 sy,  0.0 ni, 98.3 id,  1.0 wa,  0.0 hi,  0.3 si,  0.0 st 
> %Cpu1  : 51.3 us, 48.7 sy,  0.0 ni,  0.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
> %Cpu2  :  0.0 us,  0.3 sy,  0.0 ni, 99.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
> %Cpu3  :  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
> MiB Mem :   7945.1 total,   7029.1 free,    356.1 used,    675.2 buff/cache     
> MiB Swap:    200.0 total,    200.0 free,      0.0 used.   7589.0 avail Mem 
> 
>   PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                                                                                       
>  1823 root      20   0   68720  30804  14336 R  99.7   0.4   2:25.95 python3                                                                                                       
>     1 root      20   0   35900   9776   7916 S   0.0   0.1   0:00.86 systemd                                                                                                       
>     2 root      20   0       0      0      0 S   0.0   0.0   0:00.00 kthreadd                                                                                                      
> ```

If this is just for displaying CPU temperature or fan speed on the OLED display, I'm not happy.

@Lovmong
Copy link
Contributor

Lovmong commented Nov 6, 2024

We have not reproduced your problem, and the usage we tested is around 5%. Are you using the latest program? Are there any other programs running that cause conflicts?
screenshot_2024-11-06_10-46-02
screenshot_2024-11-06_10-50-36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants