From: Amit Tiwary <tiwaryamt@gmail.com>
To: ceph-devel@vger.kernel.org
Subject: Re: extremely-high-unreasonable number of threads and memory usage on the client side using librados C++ api
Date: Thu, 17 Jul 2014 05:42:32 +0000 (UTC) [thread overview]
Message-ID: <loom.20140717T073809-116@post.gmane.org> (raw)
In-Reply-To: alpine.DEB.2.00.1407160844020.28285@cobra.newdream.net
Sage Weil <sweil <at> redhat.com> writes:
> Increasing the open file limit is the way to address this currently. The
> underlying problem is that we are creating threads to service each
> connection and there isn't a max open connection limit. The real fix is
> to reimplement the SimpleMessenger, but the workaround is simple enough
> (ulimit -n) that we haven't addressed that yet. Yes, it will consume more
> resources than it probably should.. sorry about that!
>
Thanks Sage. Would eagerly await work on SimpleMessenger and other items
from this blueprint to improve threading.
https://wiki.ceph.com/Planning/Blueprints/Giant/librados%2F%2Fobjecter%3A_im
prove_threading
--
Amit Tiwary
prev parent reply other threads:[~2014-07-17 5:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 10:24 extremely-high-unreasonable number of threads and memory usage on the client side using librados C++ api Amit Tiwary
2014-07-16 15:46 ` Sage Weil
2014-07-17 5:42 ` Amit Tiwary [this message]
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=loom.20140717T073809-116@post.gmane.org \
--to=tiwaryamt@gmail.com \
--cc=ceph-devel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox