From: Christian Stroetmann <stroetmann@ontolab.com>
To: reiserfs-devel@vger.kernel.org
Subject: Re: Article [march 2010]- Reiser4 Benchmarks Against EXT4 & Btrfs
Date: Sun, 02 May 2010 14:37:11 +0200 [thread overview]
Message-ID: <4BDD71F7.8090808@ontolab.com> (raw)
In-Reply-To: <74f3961468d0562a3b42286358c95839@mail.velocitynet.com.au>
Aloha Hardcoders;
The following message was sent to Glenn at the 30.April.2010, but I
missed to hit the reiserfs-devel@vger.kernel.org button. :-[
***
Aloha Glenn;
> This may be of interest
> Reiser4 Benchmarks Against EXT4& Btrfs.
>
> http://www.phoronix.com/scan.php?page=article&item=reiser4_benchmarks&num=1
>
> Cheers
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Thank you very much for this information. I've seen somewhere else a
similar benchmark with similar results.
But I don't know for what the SQLite test is good for, because we've
already a similar working data structure as the foundation of the R4 and
forked R4 FSs and it is somekind of redundant to run SQLite or another
database like PostgreSQL on top of the R4 or and forked R4 FS, from my
point of view.
In conjunction with the database PostgreSQL it's interesting that the R4
FS crashed.
(Off-topic comment: And I don't know for what that statement should be
good which declares EXT4 as an evolutionary file system.)
Btw.: Can it be that you're a 'hardcore supporter' of R4, or even more? :-D
Have fun in the sun
Christian *<:o) O>-< -(D)>-<
***
With all the best
Christian *<:o) O>-< -(D)>-<
prev parent reply other threads:[~2010-05-02 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 2:56 Article [march 2010]- Reiser4 Benchmarks Against EXT4 & Btrfs doiggl
2010-05-02 12:22 ` Simon
2010-05-02 12:25 ` Simon
2010-05-02 12:43 ` Christian Stroetmann
2010-05-02 12:37 ` Christian Stroetmann [this message]
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=4BDD71F7.8090808@ontolab.com \
--to=stroetmann@ontolab.com \
--cc=reiserfs-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.