From: Joao Eduardo Luis <joao.luis@inktank.com>
To: Gregory Farnum <greg@inktank.com>
Cc: "Cláudio Martins" <ctpm@ist.utl.pt>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"Samuel Just" <sam.just@inktank.com>
Subject: Re: OSD and MON memory usage
Date: Mon, 19 Nov 2012 23:20:15 +0000 [thread overview]
Message-ID: <50AABEAF.5020703@inktank.com> (raw)
In-Reply-To: <CAPYLRzj95YK92KUwMnZF5W7oRJOx4kaaSL0siZ27Vt_x7d-Tzw@mail.gmail.com>
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
>
next prev parent reply other threads:[~2012-11-19 23:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 17:24 OSD and MON memory usage Cláudio Martins
2012-11-16 18:42 ` Joao Eduardo Luis
2012-11-19 23:15 ` Gregory Farnum
2012-11-19 23:20 ` Joao Eduardo Luis [this message]
2012-11-23 16:46 ` Joao Eduardo Luis
2012-11-27 17:23 ` Cláudio Martins
2012-11-28 21:00 ` Samuel Just
2012-11-28 21:05 ` Cláudio Martins
2012-11-28 21:08 ` Samuel Just
2012-11-28 21:30 ` Cláudio Martins
2012-11-28 23:13 ` Sylvain Munaut
2012-11-28 23:31 ` Cláudio Martins
2012-12-04 19:29 ` Gregory Farnum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50AABEAF.5020703@inktank.com \
--to=joao.luis@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ctpm@ist.utl.pt \
--cc=greg@inktank.com \
--cc=sam.just@inktank.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.