From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Is fossil/venti file system a good choice for SSD?
Date: Sat, 3 Feb 2018 14:53:52 +0000 [thread overview]
Message-ID: <0cd144e079b9354209187e89b8a05836@quintile.net> (raw)
In-Reply-To: <CAFSF3XNq-ofcFLG+StBJTt_rjZkFQBA2kSgJTPwkykknA+wVrg@mail.gmail.com>
More the lidea of reading from the ssd first.
The way fs(4) driver works is you order your drives
with the first written at one end of the queue and first read at the other.
I assume the read rate and rotational latency of an ssd should
be better than hdd so I get the best performace.
I should add that Erik once warned me (and I believe him) that ssds are
really no more reliable in terms of MTBF than hhds, its just that they are more
robust to impact - just in case anyone thinks they last forever...
-Steve
next prev parent reply other threads:[~2018-02-03 14:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 9:39 lchg
2018-02-03 10:54 ` Ethan Grammatikidis
2018-02-03 12:45 ` Steve Simon
2018-02-03 13:25 ` hiro
2018-02-03 14:53 ` Steve Simon [this message]
2018-02-03 16:53 ` hiro
2018-02-03 18:49 ` Digby R.S. Tarvin
2018-02-03 20:10 ` Bakul Shah
2018-02-03 21:46 ` Digby R.S. Tarvin
2018-02-03 23:46 ` Bakul Shah
2018-02-04 9:45 ` [9fans] RasPi why? Ethan Grammatikidis
2018-02-04 15:05 ` Rui Carmo
2018-02-04 16:36 ` Steve Simon
2018-02-04 21:00 ` Lyndon Nerenberg
2018-02-04 21:55 ` Bakul Shah
2018-02-04 22:23 ` hiro
2018-02-04 23:46 ` Skip Tavakkolian
2018-02-04 23:52 ` Lyndon Nerenberg
2018-02-05 9:22 ` hiro
2018-02-05 9:27 ` Rui Carmo
2018-02-05 9:48 ` hiro
2018-02-05 9:49 ` hiro
2018-02-04 10:02 ` [9fans] Is fossil/venti file system a good choice for SSD? hiro
2018-02-04 23:46 ` Bakul Shah
2018-02-05 8:50 ` hiro
2018-02-04 9:52 ` hiro
2018-02-04 16:15 ` Digby R.S. Tarvin
2018-02-04 21:46 ` hiro
2018-02-04 22:47 ` Digby R.S. Tarvin
2018-02-05 9:54 ` hiro
2018-02-04 9:49 ` hiro
2018-02-04 22:22 ` Ole-Hjalmar Kristensen
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=0cd144e079b9354209187e89b8a05836@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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).