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.

Sign up for GitHub

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

Jump to bottom

Show CPU and Memory usage #150

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Show CPU and Memory usage #150

wants to merge 1 commit into from

Conversation

Dahlgren
Copy link
Owner

@Dahlgren Dahlgren commented Jan 16, 2020 •
edited
Loading

image

image

@Frozen-byte
Copy link

I kindly suggest you to make the interval editable via settings modal or config.js

@Dahlgren Dahlgren force-pushed the feature/cpu-memory-usage branch 3 times, most recently from 0fd6d73 to 94705da Compare April 11, 2020 00:22
@Dahlgren
Copy link
Owner Author

Added CPU and RAM usage by headless clients as well in server page

@Dahlgren Dahlgren force-pushed the feature/cpu-memory-usage branch from 94705da to 5bba7bd Compare April 11, 2020 09:08
@Dahlgren Dahlgren force-pushed the feature/cpu-memory-usage branch from 5bba7bd to d39cac3 Compare December 13, 2020 13:04
@Dahlgren Dahlgren force-pushed the feature/cpu-memory-usage branch from d39cac3 to 64d0fb6 Compare December 29, 2020 23:34
@Dahlgren Dahlgren force-pushed the feature/cpu-memory-usage branch from 64d0fb6 to 33aba10 Compare February 28, 2021 12:22
@ards
Copy link

ards commented May 20, 2021

Can you please merge this in master.

@Fusselwurm
Copy link
Contributor

Fusselwurm commented May 22, 2021 •
edited
Loading

🤔 while memory usage shows good values, CPU is always at 0% for me (Windows Server 2019). Weirdly enough, it's fine on my Windows 10 machine though.

edit: ...and cpu values are fine even on the Windows Server if I start the service via "npm start", but return 0 if I start the service via the respective server control panel. I'm stumped, but I guess the code here is ok and it's some service permissions thing or something else I'm missing

edit2: fixed my problem, which was caused by limited permissions for a service user preventing it from getting system uptime... see soyuka/pidusage#130

@Frozen-byte Frozen-byte mentioned this pull request Jun 30, 2021
Open
@Dahlgren Dahlgren force-pushed the feature/cpu-memory-usage branch from 33aba10 to dddbb46 Compare July 10, 2021 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@Dahlgren @Frozen-byte @ards @Fusselwurm