1 |
On Thu, Sep 4, 2014 at 2:26 PM, Сергей <protserovsd@×××××.com> wrote: |
2 |
> You need to run Fstrim if you mounted your partition WITHOUT "discard" |
3 |
> option and did lots of changes. For example, if you installed your |
4 |
> system without "discard", do fstrim and then add "discard" to |
5 |
> /etc/fstab. |
6 |
> |
7 |
|
8 |
Just a note that depending on the SSD model, discard can have a |
9 |
substantial performance penalty with negligible benefit compared to |
10 |
just sticking fstrim in your crontab. |
11 |
|
12 |
In theory the ssd should just handle discard by making a note of what |
13 |
is trimmed and utlizing this information when needed. In practice |
14 |
many ssds handle a trim by dropping whatever they're doing and don't a |
15 |
copy/delete cycle if only part of a block is trimmed, which defeats |
16 |
the whole point of trimming in the first place. FStrim has the |
17 |
advantage of being more asynchronous and possibly being able to |
18 |
consolidate trims over a longer time-period, which could improve |
19 |
performance if the ssd isn't smart about it. |
20 |
|
21 |
Is there a really good place to go for SSD reviews/etc that actually |
22 |
takes this sort of thing into account? After getting an SSD it became |
23 |
apparently that they vary widely in terms of quality. Heck, I can't |
24 |
even tell you what the erase cycle count is from the SMART info, while |
25 |
other models seems to provide all kinds of useful info. |
26 |
|
27 |
-- |
28 |
Rich |