From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: "cheater00 ." <cheater00@gmail.com>, Liu Bo <bo.li.liu@oracle.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Bad fs performance, IO freezes
Date: Tue, 27 Oct 2015 07:44:11 -0400 [thread overview]
Message-ID: <562F638B.1040701@gmail.com> (raw)
In-Reply-To: <CA+9GZUjTt7C4rjSgui3M65S_WEQ3zsLEjw39x=_Ots=N8Jn3eg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On 2015-10-26 22:00, cheater00 . wrote:
> Hello,
> currently my computer freezes every several seconds for half a second
> or so. Using it feels like I'm playing musical chairs with the kernel.
> I have just one download happening on utorrent right now - this is
> what the graph looks like:
> http://i.imgur.com/LqhMtrJ.png
> and every time a new spike happens, a freeze happens just before
> that... that's the only time those freezes happen, too.
>
Do you have the 'autodefrag' mount option enabled? If it is turned on,
then that may be the problem. Most bittorrent clients pre-allocate the
space for a download, then write each block directly into the location
it's supposed to be in the resultant download, which means depending on
how it's pre-allocating the space, that you end up with a large number
of randomly ordered writes into a single file, which in turn will
trigger the autodefrag code, which can cause latency spikes when you're
also hitting the disk at the same time.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-10-27 11:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 12:16 Bad fs performance, IO freezes cheater00 .
2015-10-26 13:32 ` Donald Pearson
2015-10-26 13:36 ` cheater00 .
2015-10-26 13:45 ` Donald Pearson
2015-10-26 13:46 ` cheater00 .
2015-10-26 13:56 ` cheater00 .
2015-10-26 14:00 ` Donald Pearson
2015-10-26 14:25 ` Liu Bo
2015-10-26 14:38 ` cheater00 .
2015-10-26 15:40 ` cheater00 .
2015-10-26 17:43 ` cheater00 .
2015-10-26 18:31 ` cheater00 .
2015-10-27 2:00 ` cheater00 .
2015-10-27 6:39 ` Duncan
2015-10-27 8:55 ` cheater00 .
2015-10-27 11:44 ` Austin S Hemmelgarn [this message]
2015-10-27 13:00 ` Henk Slager
2015-10-27 13:30 ` Austin S Hemmelgarn
2015-10-27 14:22 ` cheater00 .
2015-10-27 14:26 ` cheater00 .
2015-10-27 14:30 ` cheater00 .
2015-10-27 14:43 ` cheater00 .
2015-10-27 15:01 ` Holger Hoffstätte
2015-10-27 15:05 ` cheater00 .
2015-10-27 15:07 ` cheater00 .
2015-10-27 15:22 ` Holger Hoffstätte
2015-10-27 15:26 ` Austin S Hemmelgarn
2015-10-29 13:03 ` cheater00 .
2015-10-29 14:00 ` Austin S Hemmelgarn
2015-10-29 15:49 ` cheater00 .
2015-10-29 18:49 ` Henk Slager
2015-10-29 20:01 ` Austin S Hemmelgarn
2015-11-06 13:37 ` cheater00 .
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=562F638B.1040701@gmail.com \
--to=ahferroin7@gmail.com \
--cc=bo.li.liu@oracle.com \
--cc=cheater00@gmail.com \
--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).