"ceph-devel"
Envoyé: Jeudi 2 Juillet 2015 05:38:24
Objet: RE: Probable memory leak in Hammer write path ?
Hi,
I think I am eventually able to figure out what is happening.. First, here is
the step to reproduce it in any kernel (not specific to 3.16/3.18 as I said
earlier)
1. In a SSD c
allocator and moving to jemalloc.
Thanks Greg for asking me to relook at tcmalloc otherwise I was kind of out of
option :-)..
Regards
Somnath
-Original Message-
From: Somnath Roy
Sent: Wednesday, July 01, 2015 4:58 PM
To: 'Gregory Farnum'
Cc: ceph-devel@vger.kernel.org
Subject: RE
y
Cc: ceph-devel@vger.kernel.org
Subject: Re: Probable memory leak in Hammer write path ?
On Mon, Jun 29, 2015 at 4:39 PM, Somnath Roy wrote:
> Greg,
> Updating to the new kernel updating the gcc version too. Recent kernel is
> changing tcmalloc version too, but, 3.16 has old tcmal
On Mon, Jun 29, 2015 at 4:39 PM, Somnath Roy 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 variabl
oing is to install ceph from ceph.com and see the
behavior.
Thanks & Regards
Somnath
-Original Message-
From: Gregory Farnum [mailto:g...@gregs42.com]
Sent: Monday, June 29, 2015 3:53 AM
To: Somnath Roy
Cc: ceph-devel@vger.kernel.org
Subject: Re: Probable memory leak in Hammer wri
PM
> To: ceph-devel@vger.kernel.org
> Subject: Probable memory leak in Hammer write path ?
>
> Hi,
> I am chasing a substantial memory leak in latest Hammer code base in the
> write path since yesterday and wanted to know if anybody else is also
> observing this or not. This is as
evel@vger.kernel.org
Subject: Probable memory leak in Hammer write path ?
Hi,
I am chasing a substantial memory leak in latest Hammer code base in the write
path since yesterday and wanted to know if anybody else is also observing this
or not. This is as simple as running a fio-rbd random_write workload i
Hi,
I am chasing a substantial memory leak in latest Hammer code base in the write
path since yesterday and wanted to know if anybody else is also observing this
or not. This is as simple as running a fio-rbd random_write workload in my
single OSD server with say block size 16K and num_jobs = 8.
