From: Chris Mason <chris.mason@oracle.com>
To: mp3geek <mp3geek@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: compression performance/scalability
Date: Wed, 15 Apr 2009 10:26:25 -0400 [thread overview]
Message-ID: <1239805585.4330.1.camel@think.oraclecorp.com> (raw)
In-Reply-To: <e6ac15e50904150644p5f768abdoddbef88c5aff31c6@mail.gmail.com>
On Thu, 2009-04-16 at 01:44 +1200, mp3geek wrote:
> I'm using btrfs (from 2.6.29.1) on my mythtv box, and I've found
> issues recording 2 channels with compression enabled. (2 seperate
> DVB-S cards, recording 2 seperate channels at the same time). One
> recording will be fine, but the other recording will be broken.. file
> is damaged and basically unplayable. Seems better when compression
> isn't enabled when saving 2 streams at the same time, both files
> record fine.. will the performance improve in the upcoming 2.6.30?
This isn't really a performance problem, that sounds like a compression
bug. I do a bunch of parallel testing on the compression code, and
streaming writes is a pretty simple workload.
So, do you have anything in dmesg about the second file? Checksum
errors or anything like that?
-chris
prev parent reply other threads:[~2009-04-15 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 13:44 compression performance/scalability mp3geek
2009-04-15 14:26 ` Chris Mason [this message]
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=1239805585.4330.1.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mp3geek@gmail.com \
/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