All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: iostat show constants write to osd disk with writeahead journal, normal behaviour ?
Date: Mon, 18 Jun 2012 08:29:58 -0500	[thread overview]
Message-ID: <4FDF2D56.7010108@inktank.com> (raw)
In-Reply-To: <de0635df-9b2a-4848-89ed-8eda179147db@mailpro>

On 6/18/12 7:34 AM, Alexandre DERUMIER wrote:
> Hi,
>
> I'm doing test with rados bench, and I see constant writes to osd disks.
> Is it the normal behaviour ? with write-ahead should write occur each 20-30 seconde ?
>
>
> Cluster is
> 3 nodes (ubuntu precise - glibc 2.14 - ceph 0.47.2) with each node 1 journal on tmpfs 8GB - 1 osd (xfs) on sas disk  - 1 gigabit link
>
>
> 8GB journal can handle easily 20s of write (1 gigabit link)
>
> [osd]
>          osd data = /srv/osd.$id
>          osd journal = /tmpfs/osd.$id.journal
>          osd journal size = 8000
>          journal dio = false
>          filestore journal parallel = false
>          filestore journal writeahead = true
>          filestore fiemap = false
>
>
>
>
> I have done tests with differents kernel (3.0,3.2,3.4) , differents filesystem (xfs,btrfs,ext4), forced journal mode to writeahead.
> Bench were done write rados bench and fio.
>
> I always have constant write since the first second of bench start.
>
> Any idea ?

Hi Alex,

Sorry I got behind at looking at your output last week.  I've created a 
seekwatcher movie of your blktrace results here:

http://nhm.ceph.com/movies/mailinglist-tests/alex-test-3.4.mpg

The results match up well with your iostat output.  Peaks and valleys in 
the writes every couple of seconds.  Low numbers of seeks, so probably 
not limited by the filestore (a quick "osd tell X bench" might confirm 
that).

I'm wondering if you increase "filestore max sync interval" to something 
bigger (default is 5s) if you'd see somewhat different behavior.  Maybe 
try something like 30s and see what happens?

Mark


  reply	other threads:[~2012-06-18 13:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9b922de7-7e17-4b9f-a388-c612b019627a@mailpro>
2012-06-18 12:34 ` iostat show constants write to osd disk with writeahead journal, normal behaviour ? Alexandre DERUMIER
2012-06-18 13:29   ` Mark Nelson [this message]
2012-06-18 14:04     ` Alexandre DERUMIER
2012-06-18 14:22       ` Mark Nelson
2012-06-18 14:47         ` Alexandre DERUMIER
2012-06-18 15:16           ` Mark Nelson
2012-06-18 15:45             ` Alexandre DERUMIER
2012-06-19  7:09             ` Alexandre DERUMIER
2012-07-02 20:56               ` Gregory Farnum
2012-07-02 21:02                 ` Sage Weil
2012-07-03  4:30                   ` Alexandre DERUMIER
2012-06-18 14:50         ` Alexandre DERUMIER
2012-06-18 15:08           ` Alexandre DERUMIER
2012-06-18 16:01   ` Tommi Virtanen
2012-06-18 16:17     ` Alexandre DERUMIER

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=4FDF2D56.7010108@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=aderumier@odiso.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.