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

High memory usage #115

Open
vulgur opened this issue Jan 30, 2018 · 5 comments
Open

High memory usage #115

vulgur opened this issue Jan 30, 2018 · 5 comments

Comments

@vulgur
Copy link

vulgur commented Jan 30, 2018

vtop always show high memory usage, mostly above 97%, which doesn't match the Activity Monitor.

activity_monitor__all_processes__and_2__vtop__node__and_site

@Eeems
Copy link

Eeems commented Feb 1, 2018

@acarl005
Copy link

acarl005 commented Mar 9, 2018

I'm not a hardcore OS guy but I'm confused about the calculation of memory usage. I'm on MacOS and Activity Monitor, htop, and gtop are all showing a memory usage around 50%, while vtop is showing 99%. Are there multiple different interpretations for memory usage? If so, in what sense is vtop's interpretation most advantageous? Not hating, just interested in understanding differences/pros/cons here. Beautiful program btw!

@jameelmoses
Copy link

@Eeems that's CPU, not memory.

@Eeems
Copy link

Eeems commented Mar 14, 2018

@jameelmoses Good catch. Upon further looking, this is a duplicate of #95
As per that issue, this is probably because vtop is included cached memory in the metric where htop and the Activity Monitor report that separately.
Upon further looking #95 seems to be a duplicate of #11 and there is an enhancement request #15 that would help with this.

@pfych
Copy link
Contributor

pfych commented Jul 23, 2018

Fix in fork #128

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

5 participants