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

2 Bugs at CPU and RAM #386

Closed
LucyDemooon opened this issue Sep 23, 2016 · 3 comments
Closed

2 Bugs at CPU and RAM #386

LucyDemooon opened this issue Sep 23, 2016 · 3 comments
Labels
bug

Comments

@LucyDemooon
Copy link

LucyDemooon commented Sep 23, 2016 •
edited
Loading

hey

have found 2 BUGS at the CPU frequency and Ram.
Ram is 1GB to high.
and CPU frequency is incorrect
see pic http://www.directupload.net/file/d/4487/vq9o55ar_png.htm
@tobbez
Copy link

tobbez commented Sep 23, 2016

The RAM is correct. 1GiB is 1024MiB:32117/1024 = 31.364 ≈ 31.4

@LucyDemooon
Copy link
Author

I do not mean the maximum value
but the current value

@tobbez
Copy link

tobbez commented Sep 23, 2016

No idea where the system monitor you use as reference gets its data. Anyway...

If one wants to calculate it the way it's currently done then rather than

usedmem = MemTotal - MemFree - Buffers - Cached

it looks like it should be:

usedmem = MemTotal + Shmem - MemFree - Buffers - Cached - SReclaimable

Shmem covers e.g. tmpfs, which is included in cache, but is not actually reclaimable.

SReclaimable is reclaimable part of Slab.

Optionally SwapCached can be subtracted as well - it's memory that was swapped out, is swapped in again, but is still also left in the swap. Essentially it can be swapped out "for free". Doesn't seem quite right to include though (and doesn't seem to be in other tools).

On kernels 3.14 and later, the MemAvailable value could possibly be used (commit).

Here's some related links:

@dylanaraps dylanaraps mentioned this issue Oct 23, 2016
Merged
jmmweismiller added a commit to jmmweismiller/tmux-mem-cpu-load that referenced this issue Jan 18, 2018
@jmmweismiller
Updated used memory calculation.
22f4db4 
Changed used memory calculation to account for shared memory in accordance with this:
KittyKatt/screenFetch#386 (comment)
@jmmweismiller jmmweismiller mentioned this issue Jan 18, 2018
Merged
@dylanaraps dylanaraps mentioned this issue Nov 1, 2019
Closed
HorlogeSkynet pushed a commit to HorlogeSkynet/archey4 that referenced this issue Mar 26, 2020
Fixes used RAM value when reading from /proc/meminfo (and fixes units)
90975d4 
Details :
* Used RAM value : <KittyKatt/screenFetch#386 (comment)>
* RAM unit : We were also computing Mebibytes, not Megabytes (see upcoming `feature/btrfs` changes for `Disk` entry).
@dylanaraps dylanaraps mentioned this issue Nov 18, 2020
Closed
@dylanaraps dylanaraps mentioned this issue Sep 24, 2021
Closed
@kristiyanivanovx kristiyanivanovx mentioned this issue Dec 26, 2021
Closed
@shdwchn10 shdwchn10 mentioned this issue Oct 24, 2022
Merged
dev-hann added a commit to dev-hann/tmux-mem-cpu-load that referenced this issue Sep 18, 2023
@dev-hann
Updated used memory calculation.
d7ff03a 
Changed used memory calculation to account for shared memory in accordance with this:
KittyKatt/screenFetch#386 (comment)
@hholst80 hholst80 mentioned this issue Dec 5, 2023
Closed
@qaqland qaqland mentioned this issue Jun 6, 2024
Closed
@qaqland qaqland mentioned this issue Aug 17, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tobbez @LucyDemooon @darealshinji