From: Thomas Mueller <thomas@chaschperli.ch>
To: ceph-devel@vger.kernel.org
Subject: Re: pg 0.xxxx on [] is laggy
Date: Wed, 30 Jun 2010 15:45:48 +0000 (UTC) [thread overview]
Message-ID: <i0forb$a8e$1@dough.gmane.org> (raw)
In-Reply-To: AANLkTini3YGPjANBw-FgWDld2J1cpe2GXsimpMI-0y1Z@mail.gmail.com
Am Wed, 30 Jun 2010 14:05:34 +0200 schrieb Sébastien Paolacci:
> Hello Sage,
>
> It actually works better when removing the old deb pacakge;)... thanks!
>
> The "pg 0.xxxx on [] is laggy" messages have also now disappeared.
>
> Here is, just for information, the obtained two processes dbench output
> (which is not so bad given the vm the system in running into): Operation
> Count AvgLat MaxLat
> ---------------------------------------- NTCreateX 1632 8.835
> 213.966 Close 1237 0.377 157.360 Rename 73
> 24.290 195.969 Unlink 291 6.514 244.166 Qpathinfo
> 1455 4.544 237.949 Qfileinfo 311 0.233 5.723
> Qfsinfo 270 1.854 110.355 Sfileinfo 168 3.090
> 34.291 Find 552 11.182 192.610 WriteX 1076
> 4.916 409.798 ReadX 2437 0.408 61.635 LockX
> 4 0.011 0.017 UnlockX 4 0.006 0.009
> Flush 140 8.630 175.423
>
> Throughput 2.88849 MB/sec 2 clients 2 procs max_latency=409.805 ms
>
> I however get the a bunch of metadata sync warnings on the cfuse side
> "10.06.30_13:16:20.556187 7f2bc5817720 client4100 fsync - not syncing
> metadata yet.. implement me"
give the kclient a try? git://ceph.newdream.net/ceph-client-
standalone.git branch unstable-backport for use with "older" kernels.
> [osd]
> debug ms = 1
> sudo = true
> osd data = /data/osd$id
> osd journal = /ceph-journal/osd$id
why not let ceph manage the whole partition without a fs inbetween ? like
osd journal = /dev/sdX1
(and remove "journal size")
> filestore journal writeahead = true
seems to be true by default (http://ceph.newdream.net/wiki/Ceph.conf ->
filestore_journal_parallel)
- Thomas
--
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:[~2010-06-30 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 12:12 pg 0.xxxx on [] is laggy Sébastien Paolacci
2010-06-29 15:58 ` Sage Weil
2010-06-30 12:05 ` Sébastien Paolacci
2010-06-30 15:45 ` Thomas Mueller [this message]
2010-06-30 20:57 ` Sébastien Paolacci
2010-06-30 18:06 ` Sage Weil
2010-06-30 21:06 ` Sébastien Paolacci
2010-06-30 22:06 ` Sage Weil
2010-07-01 23:42 ` Sébastien Paolacci
2010-07-01 23:58 ` Sage Weil
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='i0forb$a8e$1@dough.gmane.org' \
--to=thomas@chaschperli.ch \
--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.