- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It would really useful if there was some scalable_mallinfo() type of API similar to glibc's mallinfo() so that one can get some statistics of out the allocator.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you clarify, please, which particular statistics (or which use cases) you are interested in?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Things like how much system memory is being used vs how much the user has allocated would be a good start.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As for amount of used system memory, usually you do not need allocator support. You can read VmSize value from proc/status. Consider the example: https://github.com/intel/tbb/blob/tbb_2019/src/test/harness_memory.h#L57-L97
As for amount of user allocated memory, it is interesting problem. It might be not so easy to calculate it in concurrent environment without additional overhead when threads are dynamically created and destroyed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Reading the VmSize is something we're already doing but it's not accurate in terms of how much system memory that tbbmalloc is using, right?
I appreciate the difficulty in the presence of parallel allocation and deallocations. Perhaps this page is a better analogy which discusses this type of functionality in jemalloc: https://github.com/jemalloc/jemalloc/wiki/Use-Case%3A-Basic-Allocator-Statistics ;
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page