From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: linux-btrfs@vger.kernel.org
Subject: BTRFS setup advice for laptop performance ?
Date: Fri, 04 Apr 2014 10:02:27 +0200 [thread overview]
Message-ID: <2692878.dRG1K49eOP@fnix> (raw)
Hi,
I'm going to receive a new small laptop with a 500 GB 5400 RPM mechanical
"ole' rust" HD, and I plan ton install BTRFS on it.
It will have a kernel 3.13 for now, until 3.14 gets released.
However I'm still concerned with chronic BTRFS dreadful performance and still
find that BRTFS degrades much over time even with periodic defrag and "best
practices" etc.
So I'd like to start with the best possible options and have a few questions :
- Is it still recommended to mkfs with a nodesize or leafsize different
(bigger) than the default ? I wouldn't like to lose too much disk space anyway
(1/2 nodesize per file on average ?), as it will be limited...
- Is it recommended to alter the FS to have "skinny extents" ? I've done this
on all of my BTRFS machines without problem, still the kernel spits a notice
at mount time, and I'm worrying kind of "Why is the kernel warning me I have
skinny extents ? Is it bad ? Is it something I should avoid ?"
- Are there other optimization tricks I should perform at mkfs time because
thay can't be changed later on ?
- Are there other btrfstune or mount options I should pass before starting to
populate the FS with a system and data ?
- Generally speaking, does LZO compression improve or degrade performance ?
I'm not able to figure it out clearly.
TIA for the insight.
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
next reply other threads:[~2014-04-04 8:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 8:02 Swâmi Petaramesh [this message]
2014-04-04 12:33 ` BTRFS setup advice for laptop performance ? Austin S Hemmelgarn
2014-04-04 12:48 ` Swâmi Petaramesh
2014-04-04 15:51 ` Austin S Hemmelgarn
2014-04-04 20:31 ` Duncan
2014-04-07 12:18 ` Johannes Hirte
2014-04-04 15:09 ` Hugo Mills
2014-04-04 22:35 ` Swâmi Petaramesh
2014-04-05 10:12 ` Duncan
2014-04-05 11:10 ` Swâmi Petaramesh
2014-04-05 12:16 ` Duncan
2014-04-05 14:13 ` Hugo Mills
2014-04-06 9:24 ` Swâmi Petaramesh
2014-04-07 15:11 ` Austin S Hemmelgarn
2014-04-08 11:56 ` Clemens Eisserer
2014-04-08 12:05 ` Austin S Hemmelgarn
2014-04-09 10:53 ` Chris Samuel
2014-04-12 13:17 ` Marc MERLIN
2014-04-12 17:12 ` Koen Kooi
2014-04-05 14:26 ` Garry T. Williams
2014-04-05 15:06 ` Duncan
2014-04-06 15:17 ` Martin Steigerwald
2014-04-09 11:08 ` Chris Samuel
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=2692878.dRG1K49eOP@fnix \
--to=swami@petaramesh.org \
--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).