linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: "Swâmi Petaramesh" <swami@petaramesh.org>, rob@robspanton.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Performance Issues
Date: Fri, 19 Sep 2014 08:58:27 -0400	[thread overview]
Message-ID: <541C2873.3000904@gmail.com> (raw)
In-Reply-To: <1779590.cL85uaaAL2@vajra>

[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]

On 2014-09-19 08:25, Swâmi Petaramesh wrote:
> Le vendredi 19 septembre 2014, 13:18:34 Rob Spanton a écrit :
>> I have a particularly uncomplicated setup (a desktop PC with a hard
>> disk) and I'm seeing particularly slow performance from btrfs.
>
> Weeelll I have the same over-complicated kind of setup, and an Arch Linux
> BTRFS system which used to boot in some decent amout of time in the past now
> takes about 5 full minutes to just make it to the KDM login prompt, and
> another 5 minutes before KDE is fully started. Makes me think of the good ole'
> times of Windows 95 OSR2 on a 486SX with a dying 1 GB Hard disk...
Well, part of your problem might be KDE itself, it's extremely CPU 
intensive these days.  I'd suggest disabling the 'semantic desktop' 
stuff, because that tends to be the worst offender as far as soaking up 
system resources.  Also, if you recently switched to systemd, that may 
be causing some slowdown as well (journald's default settings are 
terrible for performance)
>
> Now, let me add that I had removed all snaphots, ran a full defrag, and even
> rebalanced the damn thing without any positive effect...
>
> (And yes, my HD is physically in good shape, SMART feels fully happy, and it's
> less than 75% full...)
>
> I've been using BTRFS for 2-3 years on a dozen of different systems, and if
> something doesn't surprise me at all, it's « slow performance », indeed,
> although I'm myself more accustomed to « incredibly fscking damn slow
> performance »...
It's kind of funny, but I haven't had any performance issues with BTRFS 
since about 3.10, even on the systems my employer is using Fedora 20 on, 
and those use only a Core 2 Duo Processor, DDR2-800 RAM, and SATA2 hard 
drives.
> HTH
>



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]

  reply	other threads:[~2014-09-19 12:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 12:18 Performance Issues Rob Spanton
2014-09-19 12:25 ` Swâmi Petaramesh
2014-09-19 12:58   ` Austin S Hemmelgarn [this message]
2014-09-19 12:49 ` Austin S Hemmelgarn
2014-09-19 12:59   ` Austin S Hemmelgarn
2014-09-19 13:34 ` Holger Hoffstätte
2014-09-22 11:59   ` David Sterba
2014-09-22 12:37     ` Holger Hoffstätte
2014-09-22 13:25       ` David Sterba
2014-09-19 13:51 ` Holger Hoffstätte
2014-09-19 14:53   ` Austin S Hemmelgarn
2014-09-19 16:23     ` Holger Hoffstätte
2014-09-19 17:51   ` Zach Brown
2014-09-20  8:23   ` Marc Dietrich
2014-09-20 13:41     ` Martin
2014-09-20 18:29       ` Chris Murphy
2014-09-20 14:04     ` Wang Shilong
2014-09-20 20:44       ` Marc Dietrich
2014-09-19 15:05 ` Josef Bacik
2014-09-19 16:51   ` Rob Spanton
2014-09-19 17:45     ` Josef Bacik
2014-10-30 14:23       ` Rob Spanton
2014-09-20  5:58     ` Duncan

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=541C2873.3000904@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rob@robspanton.com \
    --cc=swami@petaramesh.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).