On Mon, Jun 29, 2015 at 4:39 PM, Somnath Roy <Somnath.Roy@xxxxxxxxxxx> wrote: > Greg, > Updating to the new kernel updating the gcc version too. Recent kernel is changing tcmalloc version too, but, 3.16 has old tcmalloc but still exhibiting the issue. > Yes, the behavior is very confusing and compiler is main variable I could think of from application perspective. > If you have a 3.16/3.19 kernel, you could reproduce this following these steps. > > 1. Build ceph-hammer code base > > 2. Run with single OSD. > > 3. Create an image and run a fio-bed workload from client (say 16K bs, 8 num_jobs) > > 4. run 'dstat -m' and observe the memory usage. > > What I am thinking of doing is to install ceph from ceph.com and see the behavior. In addition to that, I'd look for if there are any known bugs in the tcmalloc version you're using on the leaky systems, and check the tcmalloc stats to see if they have a bunch of free memory which hasn't been released to the OS yet. -Greg -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
