9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] anyone put their venti on an SSD?
Date: Fri,  3 May 2013 21:59:03 -0400	[thread overview]
Message-ID: <1441f696102b2c0ed9f4145ff9ee4268@kw.quanstro.net> (raw)
In-Reply-To: <66f49243322bde940034988285697c30@rei2.9hal>

On Fri May  3 17:59:27 EDT 2013, cinap_lenrek@gmx.de wrote:
> i have 60GB intel ssd in my new fileserver holding the
> cwfs worm cache. no problems so far. but the machine is
> just up for two weeks.

as long as we're straying from venti, i'll say that i've used ssds
in ken's file server as both cache and worm drives.  there
were no problems at all.  i've mostly used various intel drives,
which have performed in accordance to all published specs.

i've also used ocz drives as boot drives to hold nvram.  no
problems.  perhaps this is the proverbial faint praise.

on the subject of ken's file server / cwfs, it makes the most sense
to me to use ssds as worm, not cache.  bandwith to the cache
isn't important as long as you don't blow the ram cache.  but
anything that isn't in the ram cache but is on the worm tends
to be randomish access.  ssds to very well at at random access,
and write once decreases pressure on many things that make
implementing a flash drive hard.

i would expect similar from venti, which has an even more random
data access pattern.

- erik



  reply	other threads:[~2013-05-04  1:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 14:19 Steve Simon
2013-05-03 14:28 ` a
2013-05-03 20:59 ` geoff
2013-05-03 21:51   ` Matthew Veety
2013-05-03 21:58   ` cinap_lenrek
2013-05-04  1:59     ` erik quanstrom [this message]
2013-05-04  4:17       ` cinap_lenrek
2013-05-04  6:17         ` erik quanstrom
2013-05-03 23:59   ` Charles Forsyth
2013-05-04  1:31     ` cinap_lenrek
2013-05-04  1:41       ` Devon H. O'Dell
2013-05-04  1:47       ` Lyndon Nerenberg
2013-05-04  1:51         ` erik quanstrom
2013-05-04  1:57           ` Lyndon Nerenberg
2013-05-04  2:00             ` erik quanstrom
2013-05-04  2:03               ` Lyndon Nerenberg
2013-05-04  2:13               ` Kurt H Maier
2013-05-04  2:17                 ` erik quanstrom
2013-05-04  5:50     ` Charles Forsyth
2013-05-04  6:22       ` Bakul Shah
2013-05-04  1:16   ` Lyndon Nerenberg
2013-05-04  1:43     ` erik quanstrom
2013-05-04  1:50       ` Lyndon Nerenberg
2013-05-04  3:41       ` Steven Stallion
2013-05-04  4:19         ` cinap_lenrek
2013-05-04  4:46           ` Lyndon Nerenberg
2013-05-04  3:26 ` Steven Stallion
2013-05-04  6:44   ` erik quanstrom
2013-05-04 18:09     ` Steven Stallion

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=1441f696102b2c0ed9f4145ff9ee4268@kw.quanstro.net \
    --to=quanstro@quanstro.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).