public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: nightrow <nightrow@gmail.com>
To: Jaime sanchez <jskartman@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Phoronix article slaming BTRFS
Date: Tue, 23 Jun 2009 19:44:43 +0200	[thread overview]
Message-ID: <4A41148B.80509@gmail.com> (raw)
In-Reply-To: <2d23818a0906231030t40adf82dh26e037b515c6aa0b@mail.gmail.com>

If you look here : http://btrfs.wiki.kernel.org/index.php/Main_Page in=20
the benchmarking section, you will notice that the test was made more=20
than one month ago.
I also mentionned, as said by chris on phoronix phorums, that kernel=20
starting from 2.6.30 should be faster.

I think we should expect them to run it periodicaly against newer versi=
on.

I made the link to the phoronix test. They may not be the best, but thi=
s=20
is all I found. If you find any better test, don't hesitate to add them=
=2E

disclaimer: I'm not a btrfs developer, just a entusiast that follows
the developement.

Jb benoit.

Jaime sanchez wrote :
> They are using 2.6.29.4 kernel, it isn't a bit old??
>
> I think that kernel doesn't have the last btrfs updates, and that it
> is a very bad work and benchmarks results from phoronix part. If u ar=
e
> benchmarking an experimental filesystem benchmark it with the lastest
> updaets =BF? it doesn't have sense.
>
>  =20



--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-06-23 17:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23  2:51 Phoronix article slaming BTRFS Mike Ramsey
2009-06-23 10:13 ` Miguel F Mascarenhas Sousa Filipe
     [not found]   ` <2d23818a0906231026g6e4567fdv8eda3d6c4828ef4d@mail.gmail.com>
2009-06-23 17:28     ` Jaime sanchez
2009-06-24  1:27       ` Mike Ramsey
2009-06-24  2:20         ` Wil Reichert
2009-06-24  2:47           ` Mike Ramsey
2009-06-24  9:31             ` Bron Gondwana
2009-06-24 12:57               ` Mike Ramsey
2009-06-25  1:32                 ` Bron Gondwana
2009-06-23 14:41 ` Chris Mason
2009-06-23 14:53   ` Sander
2009-06-23 15:17     ` Chris Mason
2009-06-23 16:19   ` Stephan von Krawczynski
2009-06-23 16:30     ` Chris Mason
2009-06-24  2:20     ` Mike Ramsey
2009-06-24  8:20       ` Sander
2009-06-24  8:31       ` Jens Axboe
2009-06-24 13:11         ` Mike Ramsey
2009-06-24 17:38           ` Jens Axboe
2009-06-25  8:43             ` Stephan von Krawczynski
2009-06-23 17:30 ` Jaime sanchez
2009-06-23 17:44   ` nightrow [this message]
2009-06-23 18:27     ` Jaime sanchez

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=4A41148B.80509@gmail.com \
    --to=nightrow@gmail.com \
    --cc=jskartman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox