On 2017-04-09 19:23, Hans van Kranenburg wrote:
On 04/08/2017 01:16 PM, Hans van Kranenburg wrote:
On 04/07/2017 11:25 PM, Hans van Kranenburg wrote:
Ok, I'm going to revive a year old mail thread here with interesting new
info:
[...]
Now, another surprise:
From the exact moment I did mount -o remount,nossd on this filesystem,
the problem vanished.
https://syrinx.knorrie.org/~knorrie/btrfs/keep/2017-04-07-ichiban-munin-nossd.png
I don't have a new video yet, but I'll set up a cron tonight and post it
later.
I'm going to send another mail specifically about the nossd/ssd
behaviour and other things I found out last week, but that'll probably
be tomorrow.
Well, there it is:
https://syrinx.knorrie.org/~knorrie/btrfs/keep/2017-04-08-ichiban-walk-nossd.mp4
Amazing... :) I'll update the file later with extra frames.
Added all new pngs up until now to the video, same link to the mp4.
Looks great! It just keeps reusing the same spots of space all the time.
When looking at this, I can understand that this is an unwanted write
pattern on a low-end ssd that was available for sale in 2008.
But, how does this apply to an SSD you can buy in 2017?
Depends on what brand and how cheap you go. For a decent brand (Intel,
Samsung, Crucial) and a reasonably good SSD (I'm partial to the Crucial
MX series), this really don't hurt as much as it used to.
I've got a couple of Crucial MX300's (released middle of last year IIRC)
which see roughly 200kB/s of writes constantly 24/7 (average write IOPS
is about 15-20, so most of the writes are around 16kB), and after about
6 months of this none of their wear-out indicators have changed since I
first checked them when I installed them. They've been running BTRFS
with LZO compression, the SSD allocator, atime disabled, and mtime
updates deferred (lazytime mount option) the whole time, so it may be a
slightly different use case than the OP from this thread.
Given this though, combined with the fact that Crucial SSD's are decent
(they're not quite on par with Samsung EVO's or the good Intel SSD's,
but they're still pretty good for the price), I'd be willing to say that
they're not anywhere near as workload sensitive as they used to be.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
