9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: bruce.ellis@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] SSDs
Date: Wed,  4 Dec 2013 23:19:57 -0500	[thread overview]
Message-ID: <6f4afaefbbd143357849b006cc027f7b@mikro> (raw)
In-Reply-To: <CAJQxxwkNJqN5dXZuYs15tbAnbqQAb8eG1_BjN==yuJwsV5CbcQ@mail.gmail.com>

On Wed Dec  4 23:13:29 EST 2013, bruce.ellis@gmail.com wrote:

> Let's start a fun thread. I wanna know about experience with SSDs and the
> bunny.
>
> Perhaps focusing on a) does it work b) is it worth it.

a) yes b) depends.

the depends part is most evident if your working set already fits
in various caches.  if i had to choose, and the object were performance,
i'd go 10gbe before ssd.

- erik



  reply	other threads:[~2013-12-05  4:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05  4:11 Bruce Ellis
2013-12-05  4:19 ` erik quanstrom [this message]
2013-12-05  4:21 ` Kurt H Maier

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=6f4afaefbbd143357849b006cc027f7b@mikro \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    --cc=bruce.ellis@gmail.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 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).