From: Abhishek Lekshmanan <abhishek@suse.com>
To: Ceph Development <ceph-devel@vger.kernel.org>
Cc: Casey Bodley <cbodley@redhat.com>
Subject: RGW Caching and admin ops
Date: Tue, 10 May 2016 14:44:14 +0200 [thread overview]
Message-ID: <87a8jyf5gh.fsf@suse.com> (raw)
Running normal rgw admin queries like `user info` or `bucket list` etc.
seemed significantly slower on the primary for a multisite cluster. On
investigating further with Casey yesterday, we found that most of the
time is spent up in setting up watchers and cleaning them up, and this
is because even for rgw admin cli ops, the cache is enabled.
For some local runs I saw an operation like:
$ time radosgw-admin user info --uid=testid > /dev/null
real 1m47.517s
user 0m0.176s
sys 0m0.132s
the same op with --rgw-cache-enabled=false completes in about ~0.1-0.2s.
Does rgw_cache serve any purpose for rgw admin cli ops?
Cheers
--
Abhishek Lekshmanan
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
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
reply other threads:[~2016-05-10 12:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87a8jyf5gh.fsf@suse.com \
--to=abhishek@suse.com \
--cc=cbodley@redhat.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 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.