From: erik quanstrom <quanstro@quanstro.net>
To: weigelt@metux.de, 9fans@9fans.net
Subject: Re: [9fans] Fossil+Venti on Linux
Date: Thu, 29 May 2008 08:26:21 -0400 [thread overview]
Message-ID: <57e30849922ae208454c17edd228ca69@quanstro.net> (raw)
In-Reply-To: <20080529091225.GA1617@nibiru.local>
>> since storage is very cheep, i think this is a good tradeoff.
>
> I'm thinking of an scale where storage isn't that cheap ...
what scale is that?
>> what problem are you trying to solve? if you are trying to go for
>> reliability, i would think it would be easier to use raid+backups
>> for data stability.
>
> Easier, yes, but more expensive (at least the iron).
not sure what you mean by this.
suppose i have 10TB to keep in a redundant fashion. with a two
machine solution, i need 20TB of disk since the only sensible way to
keep a redundant copy on a second machine is a full mirror. with
a 1 machine solution, i don't need any more disks to have a full
mirror and i have the option of raid5 which will reduce the number
of disks i need to 10TB + 1 disk. since your model is that the
storage is a significant expense, a single raid5 machine would make
more sense.
even if you are thinking of an enormous cloud with hundreds of
machines, you could halve the number of machines required by
raiding each node. if cost is an issue, reducing the number of
machines is a benefit. given constant data, fewer machines reduces
the obvious -- power, chassis, etc. but another important reduction
is network ports. once you outgrow a single 24-port switch, network
costs seem to grow in a super-linear fashion.
- erik
next prev parent reply other threads:[~2008-05-29 12:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 7:56 Enrico Weigelt
2008-05-25 14:59 ` a
2008-05-25 15:48 ` Francisco J Ballesteros
2008-05-25 20:24 ` erik quanstrom
2008-05-26 12:58 ` Enrico Weigelt
2008-05-26 14:01 ` erik quanstrom
[not found] ` <78feb60ec33f8a38ccbc38625b6ea653@quanstro.net>
2008-05-29 9:12 ` Enrico Weigelt
2008-05-29 9:27 ` Christian Kellermann
2008-05-29 12:17 ` Enrico Weigelt
2008-05-29 13:51 ` Russ Cox
2008-05-29 12:26 ` erik quanstrom [this message]
2008-05-29 13:33 ` Wes Kussmaul
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=57e30849922ae208454c17edd228ca69@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=weigelt@metux.de \
/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;
as well as URLs for NNTP newsgroup(s).