From: "Markus Roth" <Markus.Roth@uni-konstanz.de>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: Performance degeneration issues
Date: Wed, 20 Oct 2010 16:19:14 +0200 [thread overview]
Message-ID: <626d-4cbefa80-3-30be62c0@160346662> (raw)
In-Reply-To: 20101019014245.GN29677@dastard
Hello once more,
Am Dienstag 19 Oktober 2010 03:42 CEST, Dave Chinner <david@fromorbit.com> schrieb:
> Also, what's the output of of 'xfs_info <mntpt>'?
here's one
meta-data=/dev/sda3 isize=256 agcount=16, agsize=2949182 blks
= sectsz=512 attr=0
data = bsize=2048 blocks=47186912, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal bsize=2048 blocks=32768, version=1
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0
and another
meta-data=/dev/sdb1 isize=256 agcount=16, agsize=2621355 blks
= sectsz=512 attr=0
data = bsize=2048 blocks=41941680, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal bsize=2048 blocks=32768, version=1
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0
Please excuse my forgetting to post the requested information.
Used blocks differ because of different states in work process.
What I've also noticed is that compared to ext3, file-descriptors
get closed quite slowly (although that might also be a VMWare issue
as the one server running on pure hardware currently is testing ext3).
Greetings,
Markus
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-10-20 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 14:19 Markus Roth [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-19 13:36 Performance degeneration issues Markus Roth
2010-10-20 12:17 ` Peter Grandi
2010-10-18 15:07 Markus Roth
2010-10-19 1:42 ` Dave Chinner
2010-10-19 16:43 ` Peter Grandi
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=626d-4cbefa80-3-30be62c0@160346662 \
--to=markus.roth@uni-konstanz.de \
--cc=david@fromorbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox