All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Deranek <marcin.deranek@booking.com>
To: Marcin Deranek <marcin.deranek@booking.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
	stan@hardwarefreak.com, xfs@oss.sgi.com
Subject: Re: Performance degradation over time
Date: Thu, 11 Oct 2012 11:15:09 +0200	[thread overview]
Message-ID: <20121011111509.0a57372a@booking.com> (raw)
In-Reply-To: <20121011103352.4ed8bbf5@booking.com>

On Thu, 11 Oct 2012 10:33:52 +0200
Marcin Deranek <marcin.deranek@booking.com> wrote:

> I guess next step would be to use inode64..

After mounting XFS with inode64 I see performance improvement (open()
now takes ~3ms vs ~15ms previous) although it's still not something I
would expect (~150us.) On Dave's suggestion I will give a shot CentOS
6.x and see if that makes any difference although this needs to be
monitored over longer period of time to reliably tell if that make a
difference.
Regards,

Marcin

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-10-11  9:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10  8:51 Performance degradation over time Marcin Deranek
2012-10-10 13:17 ` Stan Hoeppner
2012-10-10 14:31   ` Eric Sandeen
2012-10-11  8:33     ` Marcin Deranek
2012-10-11  9:15       ` Marcin Deranek [this message]
2012-10-14 19:31         ` Peter Grandi
2012-10-10 23:37 ` Dave Chinner
2012-10-11  8:42   ` Marcin Deranek
  -- strict thread matches above, loose matches on Subject: below --
2016-03-08 14:09 Matthew Keeler
2016-03-08 16:32 ` Michal Kazior
2016-03-08 16:38   ` Matthew Keeler
2016-03-09  2:01     ` Matthew Keeler
2016-03-09  6:00       ` Michal Kazior
2016-03-09 12:46         ` Matthew Keeler
2016-03-17 11:21           ` Michal Kazior

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=20121011111509.0a57372a@booking.com \
    --to=marcin.deranek@booking.com \
    --cc=sandeen@sandeen.net \
    --cc=stan@hardwarefreak.com \
    --cc=xfs@oss.sgi.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.