-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
[Bug] Strange memory usage #119
Comments
Thanks for the issue, but unfortunately I can't really reproduce it. I don't know what htop shows, but the system monitor in Linux shows the exact same result as dashdot. Then the only thing "wrong" is, that I am using the 1024 base calculations, while writing "GB" instead of "GiB". This is not "really" wrong per-se, because "GB" (and "MB", "KB") gets used interchangeably, but it is technically wrong and confusion may arise. So I will switch to the unambiguous 1024 base measurements of "GiB", "MiB" and "KiB" to avoid any further confusion. |
## [3.5.2](MauriceNino/dashdot@v3.5.1...v3.5.2) (2022-06-16) ### Bug Fixes * **view:** change base 1024 size measurements to unambigous labels ([148f8db](MauriceNino/dashdot@148f8db)), closes [#119](MauriceNino/dashdot#119) * **view:** single drive in raid mode not shown in one page ([ac01eb3](MauriceNino/dashdot@ac01eb3))
Description of the bug
Memory usage in Dashdot : 11GB
Memory usage in free: 10GB
Memory usage in top: 73MB (but actually around 10GB)
Memory usage in htop: 3.5GB
Free and top take into account the buffer and cache, and I guess Dashdot uses similar tools.
htop shows the actual memory being used (since buffered and cached memory are reserved by the OS and not really used, from what I understand at least).
I feel like it would be more useful to display the actual memory being used, like htop does (RES and not VIRT/SHR).
Here is an interesting article I've found, hope it helps in some way
https://peteris.rocks/blog/htop/
The text was updated successfully, but these errors were encountered: