linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Wyzer <john.wyzer@gmx.de>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: abysmal performance
Date: Sat, 30 Apr 2011 22:51:05 +0200	[thread overview]
Message-ID: <1304196442-sup-4886@localhost> (raw)
In-Reply-To: <1304146193-sup-2200@localhost>


Resending this to the list since I did not notice that I just responded to
Chris Mason for the last emails...

Excerpts from John Wyzer's message of Sat Apr 30 08:57:06 +0200 2011:
> Excerpts from Chris Mason's message of Fri Apr 29 22:48:58 +0200 2011:
> > > 
> > > http://bayimg.com/NahClAadn
> > > http://bayimg.com/NahcnaADn
> > > http://bayimg.com/NAhCoAAdN
> > > http://bayimg.com/PahCaaAdN
> > 
> > Ok, you have three processes that may be causing trouble.  We probably
> > just need to defragment the files related to these three and life will
> > be good again.
> > 
> > 1) Firefox.  firefox has a bunch of little databases that are going to
> > fragment badly as we cow. 
> > 
> > 2) sup.  Is this the sup email client?
> > 
> > 3) vmware.  Are you hosting vmware virtual images on btrfs too?
> 
> @2: yes, the sup mail client, polling for messages.
> @3: yes, from some tasks I use vmware
> 
> But those were just the active applications at the time of taking the screenshot.
> I have the same thing with opera or during snapshot deletion or practically
> anything that involves some disk access.
> I'll probably get all atimes for files on my system, sort and defragment the
> files in order of importance...
> We'll see how btrfs behaves afterwards...

  parent reply	other threads:[~2011-04-30 20:51 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 14:46 abysmal performance John Wyzer
2011-04-29 15:01 ` Chris Mason
2011-04-30 17:33   ` Mitch Harder
2011-04-30 20:40     ` John Wyzer
2011-04-30 22:16       ` Mitch Harder
2011-04-30 22:33         ` John Wyzer
2011-05-03 11:05           ` Chris Mason
2011-05-03 11:06           ` Chris Mason
2011-04-30 23:55     ` Peter Stuge
2011-05-03 10:33       ` Bernhard Schmidt
2011-05-03 11:00         ` cwillu
2011-05-03 11:26           ` Bernhard Schmidt
2011-05-03 11:08         ` Chris Mason
2011-05-03 11:30           ` Bernhard Schmidt
2011-05-03 11:36             ` Chris Mason
2011-05-03 11:43               ` Bernhard Schmidt
2011-05-03 12:52                 ` Chris Mason
2011-05-03 13:03                   ` Bernhard Schmidt
2011-05-03 13:41                     ` Mitch Harder
2011-05-03 14:41                   ` Daniel J Blueman
2011-05-03 15:42                     ` Mitch Harder
2011-05-03 16:51                       ` Chris Mason
2011-05-03 14:54             ` Daniel J Blueman
2011-05-03 15:10               ` Bernhard Schmidt
     [not found]   ` <1304100271-sup-4177@localhost>
     [not found]     ` <1304100862-sup-1493@think>
     [not found]       ` <1304107977-sup-3815@localhost>
     [not found]         ` <1304110058-sup-7292@think>
     [not found]           ` <1304146193-sup-2200@localhost>
2011-04-30 20:51             ` John Wyzer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-06-20 21:51 Abysmal Performance Henning Rohlfs
2011-06-21  0:12 ` Josef Bacik
2011-06-21  7:10   ` Henning Rohlfs
2011-06-21  8:00 ` Sander
2011-06-21  9:26   ` Henning Rohlfs
2011-06-21 15:18     ` Josef Bacik
2011-06-21 16:55       ` Henning Rohlfs
2011-06-21 15:24 ` Calvin Walton
2011-06-22 14:15   ` Henning Rohlfs
2011-06-22 15:39     ` Josef Bacik
2011-06-22 15:57       ` Calvin Walton
2011-06-22 15:58         ` Josef Bacik

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=1304196442-sup-4886@localhost \
    --to=john.wyzer@gmx.de \
    --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).