From: Casey Bodley <cbodley@redhat.com>
To: "James (Fei) Liu-SSI" <james.liu@ssi.samsung.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Backend ObjectStore engine performance bench with FIO
Date: Tue, 29 Sep 2015 16:06:16 -0400 (EDT) [thread overview]
Message-ID: <727310273.23482377.1443557176794.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <720951445.22040695.1443205323581.JavaMail.zimbra@redhat.com>
Hi James/Haomai/Xiaoxi,
I spent some more time on the fio-objectstore branch, and pushed an update.
In testing, I realized that it was using the io_unit's start time to name the
objects, which meant that every write operation was creating a separate object.
In addition to fixing this to use fio's filenames for object names, I also
added support for the open_file() and close_file() functions. It now creates
objects of the proper size on startup, so read-only jobs will work normally.
It also removes its objects on exit.
On startup, it no longer calls create_collection() if it already exists, so I
was able to re-run fio jobs over and over again without having to clear the
data directory (tested with FileStore and KeyValueStore).
Casey
----- Original Message -----
> Great work James!
>
> ----- Original Message -----
> > From: "James (Fei) Liu-SSI" <james.liu@ssi.samsung.com>
> > To: "Xiaoxi Chen" <xiaoxi.chen@intel.com>, "Casey Bodley"
> > <cbodley@redhat.com>
> > Cc: "Sage Weil" <sage@newdream.net>, ceph-devel@vger.kernel.org
> > Sent: Friday, September 25, 2015 1:55:29 PM
> > Subject: Backend ObjectStore engine performance bench with FIO
> >
> > Hi Xiaoxi,
> >
> > With changing the IO mode from aio to sync, we make fio against newstore
> > works. Even with sync engine(I am still debugging the aio engine in
> > newstore with Xiaoxi) in newstore, Newstore still performing the best
> > among all of backstore engine with our initial setup(Thoroughly test
> > will
> > be run soon). Attachment is the initial data we collected for your
> > reference. Thanks for great help from Xiaoxi from regarding to Newstore
> > development to support FIO.
> >
> > Hi Casey,
> > Let me know if you need any help to put fio-ceph-objectstore into
> > upstream.
> > After then , I can commit all of mine into upstream.
>
> My pull request at https://github.com/ceph/ceph/pull/5943 is still pending.
> If you have patches that you'd like included, I would be happy to pull them
> in; just point me to a branch.
>
> >
> > Thanks,
> > James
> >
>
> Thanks,
> Casey
> --
> 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:[~2015-09-29 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99767EA2E27DD44DB4E9F9B9ACA458C03BD7EFC9@SSIEXCH-MB3.ssi.samsung.com>
2015-09-25 18:22 ` Backend ObjectStore engine performance bench with FIO Casey Bodley
2015-09-29 20:06 ` Casey Bodley [this message]
2015-09-29 21:12 ` James (Fei) Liu-SSI
2015-09-30 0:47 ` Chen, Xiaoxi
2015-09-30 13:57 ` Casey Bodley
2015-09-30 18:30 ` James (Fei) Liu-SSI
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=727310273.23482377.1443557176794.JavaMail.zimbra@redhat.com \
--to=cbodley@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=james.liu@ssi.samsung.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.