<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div style="font-family:Arial;"><br></div>
<div><br></div>
<div><br></div>
<div>On Tue, Jun 20, 2017, at 08:45 AM, Raghavendra Talur wrote:<br></div>
<blockquote type="cite"><div dir="ltr"><span class="font" style="font-family:monospace, " monospace"">Here is the data I gathered while debugging the considerable increase in memory consumption by brick process when brick multiplexing is on.<br><br>before adding 14th brick to it: 3163 MB<br>before glusterfs_graph_init is called 3171 (8 MB increase)<br>io-stats init 3180 (9 MB increase)<br>index init 3181 (1 MB increase)<br>bitrot-stub init 3182 (1 MB increase)<br>changelog init 3206 (24 MB increase)<br>posix init 3230 (24 MB increase)<br>glusterfs_autoscale_threads 3238 (8 MB increase)<br>end of glusterfs_handle_attach<br><br>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.<br><br>This is all Virtual memory data, resident memory is very nicely at 40 MB after 14 bricks.</span></div>
</blockquote><div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">Do you have the equivalent numbers for memory consumption of 14 bricks *without* multiplexing?<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;"><br></div>
</body>
</html>