CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: syncfs slower than without syncfs
Date: Wed, 07 Nov 2012 14:31:18 +0100	[thread overview]
Message-ID: <509A62A6.5070104@profihost.ag> (raw)
In-Reply-To: <509A2CE6.1010100@profihost.ag>

Am 07.11.2012 10:41, schrieb Stefan Priebe - Profihost AG:
> Hello list,
>
> syncfs is much slower than without syncfs to me.
>
> If i compile latest ceph master with wip-rbd-read:
>
> with syncfs:
> rand 4K:
>    write: io=1133MB, bw=12853KB/s, iops=3213, runt= 90277msec
>    read : io=1239MB, bw=14046KB/s, iops=3511, runt= 90325msec
> seq 4M:
>    write: io=37560MB, bw=423874KB/s, iops=103, runt= 90738msec
>    read : io=103852MB, bw=1151MB/s, iops=287, runt= 90237msec
>
> without syncfs:
> rand 4K:
>    write: io=3733MB, bw=42459KB/s, iops=10614, runt= 90039msec
>    read : io=6018MB, bw=68446KB/s, iops=17111, runt= 90038msec
> seq 4M:
>    write: io=51204MB, bw=577328KB/s, iops=140, runt= 90820msec
>    read : io=150320MB, bw=1666MB/s, iops=416, runt= 90228msec
>
> I thought syncfs should boost the performance.

Fixed - my chroot env with glibc syncfs support didn't had the libcrypto 
installed and it isn't in the control dependencies. Now with libcrypto i 
get the same results as without syncfs.

Stefan

  reply	other threads:[~2012-11-07 13:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07  9:41 syncfs slower than without syncfs Stefan Priebe - Profihost AG
2012-11-07 13:31 ` Stefan Priebe - Profihost AG [this message]
2012-11-07 15:04   ` Mark Nelson
2012-11-07 16:26     ` Stefan Priebe
2012-11-08  3:09       ` Josh Durgin
2012-11-08  8:52         ` Stefan Priebe - Profihost AG

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=509A62A6.5070104@profihost.ag \
    --to=s.priebe@profihost.ag \
    --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