From: Sander <sander@humilis.net>
To: Jim Faulkner <jfaulkne@ccs.neu.edu>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: worse than expected compression ratios with -o compress
Date: Sun, 17 Jan 2010 15:34:22 +0100 [thread overview]
Message-ID: <20100117143422.GA18448@cumulus> (raw)
In-Reply-To: <alpine.DEB.2.00.1001161048330.16549@alumni-linux.ccs.neu.edu>
Hello Jim,
Jim Faulkner wrote (ao):
> To contrast, rzip can compress a database dump of this data to
> around 7% of its original size. This is an older database dump,
> which is why it is smaller. Before:
> -rw------- 1 root root 69G 2010-01-15 14:55 mysqlurdbackup.2010-01-15
> and after:
> -rw------- 1 root root 5.2G 2010-01-16 05:34 mysqlurdbackup.2010-01-15.rz
>
> Of course it took 15 hours to compress the data, and btrfs wouldn't
> be able to use rzip for compression anyway.
The difference between a life MySQL database and a dump of that database
is that the dump is text, while the database files are binary.
A fair comparison would be to compress the actual database files.
With kind regards, Sander
--
Humilis IT Services and Solutions
http://www.humilis.net
next prev parent reply other threads:[~2010-01-17 14:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 16:16 worse than expected compression ratios with -o compress Jim Faulkner
2010-01-17 14:34 ` Sander [this message]
2010-01-18 14:46 ` Jim Faulkner
2010-01-18 16:06 ` Jim Faulkner
2010-01-18 14:12 ` Josef Bacik
2010-01-18 21:29 ` Chris Mason
2010-01-18 22:11 ` Jim Faulkner
2010-01-20 16:30 ` Chris Mason
2010-01-21 18:16 ` Jim Faulkner
2010-01-21 20:04 ` Gregory Maxwell
2010-01-21 20:07 ` Chris Mason
2010-01-21 20:05 ` Chris Mason
2010-01-21 22:38 ` Jim Faulkner
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=20100117143422.GA18448@cumulus \
--to=sander@humilis.net \
--cc=jfaulkne@ccs.neu.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.