[Gluster-devel] brick multiplexing and memory consumption

Raghavendra Talur rtalur at redhat.com
Tue Jun 20 12:45:31 UTC 2017


Here is the data I gathered while debugging the considerable increase in
memory consumption by brick process when brick multiplexing is on.

before adding 14th brick to it:             3163 MB
before glusterfs_graph_init is called       3171 (8  MB increase)
io-stats init                               3180 (9  MB increase)
index  init                                 3181 (1  MB increase)
bitrot-stub init                            3182 (1  MB increase)
changelog  init                             3206 (24 MB increase)
posix  init                                 3230 (24 MB increase)
glusterfs_autoscale_threads                 3238 (8  MB increase)
end of glusterfs_handle_attach

Every brick attach is taking about 75 MB of virtual memory and it is
consistent. Need help from respective xlators owners to confirm if init of
those xlators really takes that much memory.

This is all Virtual memory data, resident memory is very nicely at 40 MB
after 14 bricks.

Raghavendra Talur
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20170620/5c0fb309/attachment.html>

More information about the Gluster-devel mailing list