Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: zlib vs lzo uncompress speed, ssd vs nossd
Date: Wed, 27 Mar 2013 09:53:09 -0700	[thread overview]
Message-ID: <20130327165309.GA23559@merlins.org> (raw)

I just setup a new SSD with my laptop root filesystem, and at the time I
though, "eh, I'll just use zlib compression during the first copy, and then
switch to lzo afterwards to maintain write speed when I'm using the laptop
after the copy and reboot".

Now, I rebooted with the new ssd and zlib compressed rootfs, and it seemed
to boot slower than it did before with the same root files on btrfs lzo.

My mount options are back to lzo:
/dev/mapper/cryptroot / btrfs rw,noatime,compress=lzo,nossd,discard,space_cache 0 0

Is my feeling of slower boot wrong, or is zlib also noticeably slower than
lzo to read and decompress?

And separately, back a while ago, I read in multiple places that 'nossd'
actually worked better than 'ssd'. This was over a year ago now.

What's the current consensus on ssd and nosdd?
Am I correct that it mostly affects how data is layed out at write time by
btrfs?
Should I go back to trying ssd instead of nossd?

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/  

             reply	other threads:[~2013-03-27 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 16:53 Marc MERLIN [this message]
2013-03-27 21:12 ` zlib vs lzo uncompress speed, ssd vs nossd Mitch Harder
2013-03-27 21:22   ` Marc MERLIN
2013-03-27 21:33     ` Mitch Harder
2013-03-27 21:26   ` Marc MERLIN

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=20130327165309.GA23559@merlins.org \
    --to=marc@merlins.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