From: Craig Shelley <craig@microtron.org.uk>
To: reiserfs-list@namesys.com
Subject: Re: BitTorrent+Reiser4: curiouser and curiouser
Date: Mon, 25 Sep 2006 22:03:30 +0100 [thread overview]
Message-ID: <1159218210.3504.5.camel@localhost.localdomain> (raw)
In-Reply-To: <ef9ajj$ccv$1@sea.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
On Mon, 2006-09-25 at 21:27 +0200, Nicolas STRANSKY wrote:
> Le 09/22/2006 08:28 AM, David Masover a écrit :
> > Azureus had a problem. Once it got up to a good clip downloading, it
> > would thrash the disk. It would thrash the disk, and the system, so
> > hard that even web browsing was difficult, due to disk access being
> > many, many times slower than Internet access, even an Internet which is
> > being hogged by BitTorrent.
>
> Just to add my 2¢, I have exactly the same problem with azureus + r4.
> Azureus starts to make constant disk writes at ~500-700kB/s when
> downloading a file on a r4 partition.
> I had opened a bugreport for azureus, but it now appears that this
> problem is reiser4 specific as I cannot reproduce it with other filesystems.
> https://sourceforge.net/tracker/?func=detail&atid=575154&aid=1558227&group_id=84122
>
I get this problem too. I believe I first noticed it when the fsync
trouble started.
--
Craig Shelley
EMail: craig@microtron.org.uk
Jabber: shell@jabber.earth.li
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-25 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 6:28 BitTorrent+Reiser4: curiouser and curiouser David Masover
2006-09-22 8:45 ` Alexander Zarochentsev
2006-09-22 17:23 ` David Masover
2006-09-22 9:26 ` Konstantin Münning
2006-09-22 17:20 ` David Masover
2006-09-22 21:01 ` Milan Holzäpfel
2006-09-25 19:27 ` Nicolas STRANSKY
2006-09-25 21:03 ` Craig Shelley [this message]
2006-10-02 15:39 ` rvalles
[not found] ` <20061002153947.GB12563@rvalles.homedns.org>
2006-10-03 3:47 ` Christopher Sawtell
2006-10-05 3:08 ` rvalles
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=1159218210.3504.5.camel@localhost.localdomain \
--to=craig@microtron.org.uk \
--cc=reiserfs-list@namesys.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 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.