Mailinglist Archive: opensuse (1786 mails)
| < Previous | Next > |
Re: [opensuse] SSD in openSUSE.
- From: C <smaug42@xxxxxxxxxxxx>
- Date: Wed, 23 Nov 2011 10:05:28 +0100
- Message-id: <CAOVv=gOWDqFidn5MeDwT_GZQ0qT2vpv9rvzhTv3da-r7m5NnpA@mail.gmail.com>
On Wed, Nov 23, 2011 at 09:16, Hans Witvliet <suse@xxxxxxxxxxx> wrote:
Why is everyone still perpetuating the belief that Flash based SSDs
still need this careful management of write cycles? Do the math...
with current SSDs and their write cycle ratings (a current/new SSD
does not have a write cycle rating of 10,000 like they did 4 or 5
years ago... you are looking at 5,000,000 or more write cycles now),
you would have to basically do many hundreds of GBs (or even several
TB on larger drives) of writing every single day for 40 to 50 years or
even more to hit the write access barriers. Everyone is basing this
whole "I have to minimize write cycles" thing on SSD specs of several
years ago.
Same goes for setting aside 15% of the SSD for "spare" space.
Many/most SSD manufacturers already do this, so as a user you should
be able to just use whatever you see as available space and not worry
about it.
All this fiddling and worrying about write cycles and extra leftover
buffer space may make sense on a server storage deployment, but for a
home user, you'd have to try really really really hard to hit the
barrier even with /swap, /tmp, /var on the SSD.
Basically, buy a good quality SSD and don't worry about it.
C.
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx
On Tue, 2011-11-22 at 22:40 +0100, Smartysmart34 wrote:
I use an SSD with openSuse 11.4 and had no problems so far. To minimise
write-access and to support TRIM on that SSD I did the following:
1) Mounted / with "discard"-Option
2) Moved SWAP, var and temp to a separate disk
3) home has been on a separate disk from the beginning and it still is
System running fine for allmost 6 months now.
Be sure to minimalize write access. I forgot once.
On a 11.3 system swap was stil active,
After a zypper dup towards 11.4 the sdd gave that many seek/read errors,
that the sdd wasn't usable anymore.
Why is everyone still perpetuating the belief that Flash based SSDs
still need this careful management of write cycles? Do the math...
with current SSDs and their write cycle ratings (a current/new SSD
does not have a write cycle rating of 10,000 like they did 4 or 5
years ago... you are looking at 5,000,000 or more write cycles now),
you would have to basically do many hundreds of GBs (or even several
TB on larger drives) of writing every single day for 40 to 50 years or
even more to hit the write access barriers. Everyone is basing this
whole "I have to minimize write cycles" thing on SSD specs of several
years ago.
Same goes for setting aside 15% of the SSD for "spare" space.
Many/most SSD manufacturers already do this, so as a user you should
be able to just use whatever you see as available space and not worry
about it.
All this fiddling and worrying about write cycles and extra leftover
buffer space may make sense on a server storage deployment, but for a
home user, you'd have to try really really really hard to hit the
barrier even with /swap, /tmp, /var on the SSD.
Basically, buy a good quality SSD and don't worry about it.
C.
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx
| < Previous | Next > |