From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joao Eduardo Luis Subject: Re: OSD and MON memory usage Date: Mon, 19 Nov 2012 23:20:15 +0000 Message-ID: <50AABEAF.5020703@inktank.com> References: <20121116172401.ef3e5e52.ctpm@ist.utl.pt> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mail-wg0-f44.google.com ([74.125.82.44]:53564 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752886Ab2KSXUd (ORCPT ); Mon, 19 Nov 2012 18:20:33 -0500 Received: by mail-wg0-f44.google.com with SMTP id dr13so3161051wgb.1 for ; Mon, 19 Nov 2012 15:20:32 -0800 (PST) In-Reply-To: Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Gregory Farnum Cc: =?ISO-8859-1?Q?Cl=E1udio_Martins?= , "ceph-devel@vger.kernel.org" , Samuel Just On 11/19/2012 11:15 PM, Gregory Farnum wrote: > Can you restart your monitor, then run "ceph heap start_profiler", and > then once the memory has gone way up run "ceph heap dump"? You should > find some files in the same directory as your monitor log files that > you can analyze using tcmalloc's tools (see > http://ceph.com/wiki/Memory_Profiling for some info), or send them our > way for analysis. > This will go easier if you also have Ceph's debug symbol packages installed. :) The wiki has been somewhat officially deprecated and is now redirecting to the docs. That page can still be accessed through http://ceph.com/deprecated/Memory_Profiling > -Greg > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >