From: Nicholas Steeves <nsteeves@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: wow!
Date: Sat, 24 Oct 2015 22:12:55 -0400 [thread overview]
Message-ID: <562C3AA7.9060007@gmail.com> (raw)
Hi,
I upgraded to linux-4.2.3 and btrfs-progs-4.2.3 yesterday, and wow,
there must have been bigger between linux-4.1.10 and 4.2.3 than were
mentioned in the changelog! I've been testing btrfs on a Thinkpad X200
with an i5-2450M, Intel 320 SSD, and 8GB of RAM for over a year now,
since when when linux-3.16 and btrfs-progs-3.17 were very new.
Performance had been steadily degrading, or hit or miss (I'm not sure if
defrag or fstrim actually work...), but stability was getting better.
The regular use case I use a benchmark is how fast the backup goes. If
the numbers seem unusual, I'll reboot and run:
tar cf- /.snapshots/only_one_snapshot | pv -pabet > /dev/null
then reboot and run
btrfs send /.snapshots/only_one_snapshot | pv -pabet > /dev/null
The worst run I've seen this last year for both of these commands~60
MiB/s throughput to /dev/null...
A year ago, when the file system was brand new, after I filled the fs
with my regular data, the average was:
GNU tar: ~125 MiB/s
BSD tar: ~129 MiB/s
btrfs send: ~140 MiB/s
Now with linux-4.2.3 and btrfs-progs-4.2.3:
GNU tar: ~134 MiB/s
BSD tar: ~129 MiB/s
btrfs send: ~133 MiB/s
This is the first time a backup has run at the speed of a fresh
filesystem; I have not recently run fstrim or btrfs fi defrag, so I was
very pleasantly surprised! Thank you all very much for your hard work.
Kind regards,
Nicholas
reply other threads:[~2015-10-25 2:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=562C3AA7.9060007@gmail.com \
--to=nsteeves@gmail.com \
--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).