memory measurement : different value between top/ps and mallinfo

[lxu4net]

There's a huge hash table in my application. I use it as a main
memory database. A lot of client write random data into the hash
table, so it call a lot of malloc() / free(). But after it run for
days, I watched it used a lot of memory. Finally it failed to call
malloc (). I use mallinfo() to watch the detail info. I found the
memory usage is different between the RSS value of "top" and
mallinfo().
"top" / "ps" tell me the application memory usage is 1.8G, but
mallinfo() say mallinfo.arena + mallinfo.hblkhd=1G.
Then I use pmap to see detail infomation. The "pmap" report 800M
"anon" blocks.

What's the "anon" blocks that "pmap" reported? Are they memory leak
or fragmentation? How can I avoid it?

 

[lxu4net]

My software env is SUSE 10 (with GCC and libc).

 

[Keith Thompson]

There's a huge hash table in my application. I use it as a main
memory database. A lot of client write random data into the hash
table, so it call a lot of malloc() / free(). But after it run for
days, I watched it used a lot of memory. Finally it failed to call
malloc (). I use mallinfo() to watch the detail info. I found the
memory usage is different between the RSS value of "top" and
mallinfo().
"top" / "ps" tell me the application memory usage is 1.8G, but
mallinfo() say mallinfo.arena + mallinfo.hblkhd=1G.
Then I use pmap to see detail infomation. The "pmap" report 800M
"anon" blocks.

What's the "anon" blocks that "pmap" reported? Are they memory leak
or fragmentation? How can I avoid it?

The C language doesn't refer to mallinfo, RSS, top, ps, pmap, or
"anon" blocks. Try asking in a forum that deals with your system,
perhaps comp.unix.programmer or one of the Linux groups.

 

[lxu4net]

I found the mallinfo() only give main arena info. malloc_stats() can
give all arena info.

 

[lxu4net]

I found the mallinfo() only give main arena info. malloc_stats() can
give all arena info.