linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Snapshots slowing system
Date: Sat, 19 Mar 2016 00:59:55 +0000 (UTC)	[thread overview]
Message-ID: <pan$600af$ffbeaf34$fd26bb3f$b784c5c1@cox.net> (raw)
In-Reply-To: 56EC4EFE.5000105@gmail.com

Austin S. Hemmelgarn posted on Fri, 18 Mar 2016 14:54:54 -0400 as
excerpted:

> As of right now, the top three brands of SSD as far as quality IMHO are
> Intel, Samsung, and Crucial.  I usually go with Crucial myself because
> they are almost on-par with the other two, give more deterministic
> performance (their peak performance is often lower, but I'm willing to
> sacrifice a bit of performance to get consistency across operating
> conditions), and cost less (sometimes less than half as much as an
> equivalently sized Intel or Samsung SSD) .  Kingston, SanDisk, ADATA,
> Transcend, and Micron are generally OK, but sometimes have issues with
> data loss when they lose power unexpectedly (this likely won't be an
> issue for you though if you have a system that's on 24/7).  The only
> brand I would actively avoid is OCZ, as they've had numerous issues with
> reliability and data integrity over multiple revisions of multiple
> models of SSD.

Thanks.  This is useful information for me as well, because while I'm not 
in the /immediate/ market for SSDs ATM, I'm relatively likely to be doing 
some new machines later this year, and will likely either be getting new 
ssds for them or will be getting newer and bigger for my main machine and 
will be putting the current 256 GiB main machine ssds in the smaller 
machines.  So I was recently looking at prices on pricewatch.com, and 
wondering again about brands.  I got relatively lucky with my first ssds 
purchased some years ago when I knew little about them (except that one 
went bad prematurely, but it has been replaced with one of the others 
now), but know much more about the technology now.  Only thing is I knew 
nothing about which brands were in general good or to stay away from, in 
ordered to narrow down the search a bit, so this was really helpful, 
particularly the Crucial bit as I already know Intels aren't 
realistically in my price range.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2016-03-19  1:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 23:03 Snapshots slowing system pete
2016-03-15 15:52 ` Duncan
2016-03-15 22:29   ` Peter Chant
2016-03-16 11:39     ` Austin S. Hemmelgarn
2016-03-17 21:08       ` Pete
2016-03-18  9:17         ` Duncan
2016-03-18 11:38           ` Austin S. Hemmelgarn
2016-03-18 17:58             ` Pete
2016-03-18 23:58             ` Duncan
2016-03-18 18:16           ` Pete
2016-03-18 18:54             ` Austin S. Hemmelgarn
2016-03-19  0:59               ` Duncan [this message]
2016-03-19  1:15             ` Duncan
  -- strict thread matches above, loose matches on Subject: below --
2016-03-12 13:01 pete
2016-03-13  3:28 ` Duncan
2016-03-11 20:03 Pete
2016-03-11 23:38 ` boris

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='pan$600af$ffbeaf34$fd26bb3f$b784c5c1@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    /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).