From: Casier David <casierdavid@gmail.com>
To: ceph-devel@vger.kernel.org
Subject: Perfomance CPU and IOPS
Date: Sun, 24 May 2015 13:21:40 +0200 [thread overview]
Message-ID: <5561B444.6060108@gmail.com> (raw)
Hello everybody,
I have some suggestions to improve the Ceph performance with in case of
using Rados Block Device.
On FileStore :
- Remove all metadata in HDD and used omap on SSD. This reduce IOPS
and increases throughput.
- Remove journal, thread "sync_entry", and write directly in
queue_transaction.
To compensate journal, you could use Cache Tier Ceph.
ceph-osd must be with less Thread and Lock.
With 1 OSD for 1 HDD, i think Lock is necessary only for scrub, recovery
or other background job.
And only one thread with the use of libaio.
I think Ceph-OSD should be very light.
Potentially with direct writing aftergiven the transmitted data to other
OSD from map.
In this case, a lot of ceph-osd could work on the same server.
Actually, i work on the repository https://www.github.com/dcasier/ceph.
You could see start works on FileStore.*
But potentially not safe.
David.
next reply other threads:[~2015-05-24 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 11:21 Casier David [this message]
2015-05-24 12:09 ` Perfomance CPU and IOPS Mark Nelson
2015-05-24 15:55 ` Casier David
2015-05-26 8:34 ` Somnath Roy
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=5561B444.6060108@gmail.com \
--to=casierdavid@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 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.