Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's worse. No line of /proc/meminfo has that value, and since not all of the cache can be instantly discarded (I didn't know that), I don't see any combination of them that would help.

That sentence:

> There are no downsides, except for confusing newbies.

Just isn't true. There is the downside that we can't know how much memory is available.



Yeah, and obviously some (though not all) forms of shared memory are actually implemented using tmpfs behind the scenes which makes life even more interesting. I think the problem I encountered involved SysV shared memory which isn't backed by tmpfs and does show up in /proc/meminfo, whereas other types may not.


Can't you use something like this: https://raw.github.com/pixelb/ps_mem/master/ps_mem.py

I use that to help determine "least incorrect" ram usage on linux. It is ok, maybe not perfect but it at least lets you get a better view on memory.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: