Linux monitor memory usage5/31/2023 ![]() This is the best explanation I could find, but mem isn't addressed there. TCP: inuse 48 orphan 49 tw 63 alloc 2620 mem 248 To find the actual memory usage, /proc/net/sockstat is the most promising: sockets: used 3640 This page writes, "the 'buffers' memory is memory used by Linux to buffer network and disk connections." This implies that they're not part of the RES metric in top. I realize one possible answer is "trust the kernel to do this for you," but I want to rule out TCP buffers as a source of memory pressure. ![]() Do the buffers continue to take up some memory even when there's minimal traffic flowing, or do they grow dynamically, with the buffer sizes merely being the maximum allowable size?.If I want to reduce it on a per-process level, how do I ensure that my reductions are having the desired effect?.Where is the memory reported? Is it part of the buff/cache item in top, or is it part of the process's RES metric?.TCP buffers are one possible culprit, but I can't make a dent in these questions: It's a bit memory constrained so I'm trying to figure out where a few hundred MBs are going. I've got a front end machine with about 1k persistent, very low-bandwidth TCP connections.
0 Comments
Leave a Reply. |