public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Hamish Moffatt <hamish@cloud.net.au>
Cc: linux-mtd@lists.infradead.org
Subject: Re: choosing a file system to use on NAND/UBI
Date: Mon, 07 Apr 2008 11:41:05 +0300	[thread overview]
Message-ID: <1207557665.8040.81.camel@sauron> (raw)
In-Reply-To: <20080407073227.GA6317@cloud.net.au>

On Mon, 2008-04-07 at 17:32 +1000, Hamish Moffatt wrote:
> I switched my UBIFS from the default lzo to zlib compression, as the
> resulting images (from mkfs.ubifs) were smaller. Is there any reason to
> prefer the default lzo?

Just FYI, although zlib compresses better, it is slower as well.
According to Richard: 

"This is particularly useful for jffs2 where significant boot time
speedups (~10%) and file read speed improvements (~40%) are seen when
its used with only a slight drop in file compression ratio."

AFAIK, the figures were related to Nokia N800. I guess for "desktop" CPU
this would not make such a big difference.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  parent reply	other threads:[~2008-04-07  8:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28  1:04 choosing a file system to use on NAND/UBI Hamish Moffatt
2008-03-28  6:33 ` Artem Bityutskiy
2008-04-07  5:12   ` Hamish Moffatt
2008-04-07  7:13     ` Artem Bityutskiy
2008-04-07  7:32       ` Hamish Moffatt
2008-04-07  7:48         ` Hamish Moffatt
2008-04-07  7:56         ` Artem Bityutskiy
2008-04-07 11:20           ` Hamish Moffatt
2008-04-07 12:15             ` Artem Bityutskiy
2008-04-07 12:16               ` Artem Bityutskiy
2008-04-07 12:22               ` Hamish Moffatt
2008-04-07 12:44                 ` Artem Bityutskiy
2008-04-07 15:31                   ` Jamie Lokier
2008-04-08 10:21                   ` Hamish Moffatt
2008-04-07  8:41         ` Artem Bityutskiy [this message]
2008-04-08  7:07         ` Artem Bityutskiy
2008-03-28  7:22 ` Adrian Hunter

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=1207557665.8040.81.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=hamish@cloud.net.au \
    --cc=linux-mtd@lists.infradead.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