From: Hans Reiser <reiser@namesys.com>
To: Heinz-Josef Claes <hjclaes@web.de>
Cc: reiserfs-list@namesys.com
Subject: Re: How to build a big file server
Date: Thu, 05 Jun 2003 17:38:17 +0400 [thread overview]
Message-ID: <3EDF47C9.1000309@namesys.com> (raw)
In-Reply-To: <1054804624.1997.39.camel@wusel.schnulli.de>
Heinz-Josef Claes wrote:
>Am Don, 2003-06-05 um 11.04 schrieb Oleg Drokin:
>
>
>>Hello!
>>
>>On Thu, Jun 05, 2003 at 10:50:15AM +0200, Heinz-Josef Claes wrote:
>>
>>
>>>>>My guess is that the writes to the journal _would_ be a problem, and
>>>>>that writing them to a seperate (RAID1)-device would help significantly.
>>>>>
>>>>>
>>>>And with journal on battery-backed RAM it would be even faster ;)
>>>>
>>>>
>>>The target is to have a cheep solution :/
>>>
>>>
>>The cheapest solution to get speed is to put journal and all data on ramdisk
>>(or even into ramfs).
>>This is not the safest one, though.
>>
>>
>>
>Perhaps this is a good idea. I'll try to test the performance. Since the
>servers are only used for an (additional) online backup (like
>snapshots), there will not be really critical data on them. I'll see if
>the performance win is worth the risk :-)
>
This sounds like a bad idea to me. If you want to gain performance,
don't do raid 5, or use a controller with a writeback cache. Frankly I
doubt you will be disk performance bound anyway.
>
>BTW: Some weeks ago there where questions about the performance of
>NetApp. I think I will have the possibility to repeat the tests with a
>filer. I'll post the results to the list, if somebody is interested.
>
>
>>Bye,
>> Oleg
>>
>>
>>
>
>
>
>
>
--
Hans
next prev parent reply other threads:[~2003-06-05 13:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 8:14 How to build a big file server Heinz-Josef Claes
2003-06-05 8:25 ` Carl-Daniel Hailfinger
2003-06-05 8:55 ` Andreas Dilger
2003-06-05 9:51 ` Hendrik Visage
2003-06-05 8:33 ` Ragnar Kjørstad
2003-06-05 8:42 ` Heinz-Josef Claes
2003-06-05 8:45 ` Marc-Christian Petersen
2003-06-05 9:30 ` Heinz-Josef Claes
2003-06-05 11:27 ` Bill Rees
2003-06-10 13:28 ` myciel
2003-06-10 13:36 ` Heinz-Josef Claes
2003-06-10 14:13 ` myciel
2003-06-12 20:34 ` Lars O. Grobe
2003-06-05 8:46 ` Oleg Drokin
2003-06-05 8:50 ` Heinz-Josef Claes
2003-06-05 9:04 ` Oleg Drokin
2003-06-05 9:17 ` Heinz-Josef Claes
2003-06-05 10:29 ` Russell Coker
2003-06-05 10:45 ` Heinz-Josef Claes
2003-06-05 16:47 ` Carl-Daniel Hailfinger
2003-06-05 17:01 ` Soeren Sonnenburg
2003-06-05 17:06 ` Ragnar Kjørstad
2003-06-06 9:41 ` Heinz-Josef Claes
2003-06-05 13:38 ` Hans Reiser [this message]
2003-06-05 12:06 ` Heinz-Josef Claes
2003-06-05 9:45 ` Christophe Saout
2003-06-05 10:07 ` Soeren Sonnenburg
2003-06-05 9:59 ` Russell Coker
2003-06-05 10:13 ` Heinz-Josef Claes
2003-06-05 10:25 ` Russell Coker
2003-06-05 10:38 ` Heinz-Josef Claes
2003-06-05 11:11 ` Russell Coker
2003-06-05 13:48 ` Chris Mason
2003-06-14 11:11 ` data-logging for 2.4.21+ (was Re: How to build a big file server) Manuel Krause
2003-06-05 10:05 ` How to build a big file server Hans Reiser
2003-06-05 10:24 ` Heinz-Josef Claes
2003-06-05 13:43 ` Sam Vilain
2003-06-05 13:55 ` Heinz-Josef Claes
2003-06-06 11:15 ` Vitezslav T. Se'm
2003-06-06 15:15 ` Russell Coker
2003-06-06 11:16 ` Vitezslav T. Se'm
[not found] <no.id>
2003-06-05 23:49 ` The Amazing Dragon
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=3EDF47C9.1000309@namesys.com \
--to=reiser@namesys.com \
--cc=hjclaes@web.de \
--cc=reiserfs-list@namesys.com \
/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.