All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs performance with small blocksize on SSD
Date: Mon, 25 Sep 2017 10:36:31 +0200	[thread overview]
Message-ID: <20170925103631.1dce28ae@jupiter.sol.kaishome.de> (raw)
In-Reply-To: a7bde40e8fa8416c888e8c65a7442b65@rwth-aachen.de

Am Mon, 25 Sep 2017 07:04:14 +0000
schrieb "Fuhrmann, Carsten" <carsten.fuhrmann@rwth-aachen.de>:

> Well the correct translation for "Laufzeit" is runtime and not
> latency. But thank you for that hint, I'll change it to "gesamt
> Laufzeit" to make it more clear.

How about better translating it to English in the first place as you're
trying to reach an international community?

Also, it would be nice to put the exact test you did as a command line
or configuration file, so it can be replayed on other systems, and -
most important - by the developers, to easily uncover what is causing
the behavior...


> Best regards
> 
> Carsten
> 
> -----Ursprüngliche Nachricht-----
> Von: Andrei Borzenkov [mailto:arvidjaar@gmail.com] 
> Gesendet: Sonntag, 24. September 2017 18:43
> An: Fuhrmann, Carsten <carsten.fuhrmann@rwth-aachen.de>; Qu Wenruo
> <quwenruo.btrfs@gmx.com>; linux-btrfs@vger.kernel.org Betreff: Re:
> AW: Btrfs performance with small blocksize on SSD
> 
> 24.09.2017 16:53, Fuhrmann, Carsten пишет:
> > Hello,
> > 
> > 1)
> > I used direct write (no page cache) but I didn't disable the Disk
> > cache of the HDD/SSD itself. In all tests I wrote 1GB and looked
> > for the runtime of that write process.  
> 
> So "latency" on your diagram means total time to write 1GiB file?
> That is highly unusual meaning for "latency" which normally means
> time to perform single IO. If so, you should better rename Y-axis to
> something like "total run time".
> N_____r__y____b_X____v_^_)__{.n_+____{_n___)____w*\x1fjg___\x1e_______j/___z_____2_______&_)___a__\x7f__\x1e_G___h_\x0f_j:+v___w____


-- 
Regards,
Kai

Replies to list-only preferred.



  reply	other threads:[~2017-09-25  8:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-24 13:24 Btrfs performance with small blocksize on SSD Fuhrmann, Carsten
2017-09-24 13:40 ` Qu Wenruo
2017-09-24 13:53   ` AW: " Fuhrmann, Carsten
2017-09-24 14:10     ` Qu Wenruo
2017-09-24 14:22       ` AW: " Fuhrmann, Carsten
2017-09-24 16:43     ` Andrei Borzenkov
2017-09-24 20:39       ` Kai Krakow
2017-09-25  7:04       ` AW: AW: " Fuhrmann, Carsten
2017-09-25  8:36         ` Kai Krakow [this message]
2017-09-26 20:33 ` Peter Grandi

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=20170925103631.1dce28ae@jupiter.sol.kaishome.de \
    --to=hurikhan77@gmail.com \
    --cc=linux-btrfs@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.