From: John Spray <john.spray@redhat.com>
To: "Yan, Zheng" <ukernel@gmail.com>,
Barclay Jameson <almightybeeij@gmail.com>
Cc: Gregory Farnum <greg@gregs42.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Slow file creating and deleting using bonnie ++ on Hammer
Date: Tue, 26 May 2015 12:57:23 +0100 [thread overview]
Message-ID: <55645FA3.3090507@redhat.com> (raw)
In-Reply-To: <CAAM7YAnxOp3Yo+F=mP4AvZBM1-7xD_N8A8h_H0cVNjOZ=S=cfg@mail.gmail.com>
On 26/05/2015 07:55, Yan, Zheng wrote:
> the reason for slow file creations is that bonnie++ call fsync(2)
> after each creat(2). fsync() wait for safe replies of the create
> requests. MDS sends safe reply when log event for the request gets
> journaled safely. MDS flush the journal every 5 seconds
> (mds_tick_interval). So the speed of file creation for bonnie++ is one
> file every file seconds.
Ah, I hadn't noticed that the benchmark called... I wonder if I'm seeing
the fuse client return quickly because it simply doesn't implement the
fsyncdir call. We should fix that!
It looks like we used to have an OP_FSYNC in the client-server protocol
(perhaps for flushing the log immediately on fsyncs), anyone have any
background on why that went away?
Cheers,
John
next prev parent reply other threads:[~2015-05-26 13:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 18:15 Slow file creating and deleting using bonnie ++ on Hammer Barclay Jameson
2015-05-20 18:22 ` Gregory Farnum
2015-05-20 19:00 ` Barclay Jameson
2015-05-22 15:25 ` Barclay Jameson
2015-05-22 15:34 ` John Spray
2015-05-22 17:34 ` Barclay Jameson
2015-05-26 6:55 ` Yan, Zheng
2015-05-26 11:57 ` John Spray [this message]
2015-05-26 14:08 ` Mark Nelson
2015-05-26 14:30 ` Gregory Farnum
2015-05-26 14:50 ` Barclay Jameson
2015-05-26 15:40 ` John Spray
2015-05-26 15:54 ` Barclay Jameson
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=55645FA3.3090507@redhat.com \
--to=john.spray@redhat.com \
--cc=almightybeeij@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@gregs42.com \
--cc=ukernel@gmail.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.