linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS setup advice for laptop performance ?
Date: Sat, 12 Apr 2014 19:12:48 +0200	[thread overview]
Message-ID: <libs6f$q4i$1@ger.gmane.org> (raw)
In-Reply-To: <20140412131710.GR7322@merlins.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marc MERLIN schreef op 12-04-14 15:17:
> On Fri, Apr 04, 2014 at 04:09:06PM +0100, Hugo Mills wrote:
>>> - Generally speaking, does LZO compression improve or degrade
>>> performance ? I'm not able to figure it out clearly.
>> 
>> Yes, it improves or degrades performance. :)
>> 
>> It'll depend entirely on what you're doing with it. If you're storing
>> lots of zeroes (Phoronix, I'm looking at you), then you'll get huge
>> speedups. If you're storing video data, you'll get a (very) slight
>> performance drop as it scompresses the first few blocks of the file and
>> then gives up. I suspect that in general, the performance differences
>> won't be noticable unless you have highly compressible large files, but
>> if you _really_ care about it, benchmark it(*).
>> 
>> Hugo.
>> 
>> (*) If you don't want to go through the effort of benchmarking, you 
>> don't care enough about it, and should just pick something at random.
> 
> Speaking of this bit, I once tried to use zlib instead of lzo, and
> somehow it felt that my laptop on SSD booted noticeably slower after
> that, which felt weird since decompression speed should be about the
> same.
> 
> Has anyone else noticed anything like this?

LZO should decompress a lot faster than zlib, I know that's the case on ARM
and 32bit x86.

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFTSXQQMkyGM64RGpERAtTRAJ9WQg0xA3s3AA+jMryzn6PVWpyEegCbBZTR
IzOZtgJvMbLT2fXdw0fOCxQ=
=2FXK
-----END PGP SIGNATURE-----


  reply	other threads:[~2014-04-12 17:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04  8:02 BTRFS setup advice for laptop performance ? Swâmi Petaramesh
2014-04-04 12:33 ` 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 [this message]
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='libs6f$q4i$1@ger.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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).