From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: fragmentation question
Date: Thu, 09 Sep 2010 23:57:36 -0500 [thread overview]
Message-ID: <4C89BAC0.4000607@hardwarefreak.com> (raw)
In-Reply-To: <4C89A4AE.2070904@hardwarefreak.com>
Stan Hoeppner put forth on 9/9/2010 10:23 PM:
> Brady Chang put forth on 9/9/2010 4:59 PM:
>> thanks guys for the feedback.
>> iostat shows balanced io between two filesystems.
>
> Can we please see the "iostat -x" output for the duration of the TPC-H
> run _only_?
What db engine are you using? Oracle, DB2, MySQL, or PostgreSQL?
Exactly how are you instructing it to split files between /data1 and /data2?
Are you instructing your db engine to split your transaction logs and db
files equally across both filesystems?
On which filesystem are you locating your database engine scratch space
if any?
Can you run xfs_bmap on the files on each filesystem to determine which
are the most fragmented? Doing this may/should produce the smoking gun.
At this point, I'm guessing you have transaction logs and db scratch
space allocated to /data2 which is causing the heavy fragmentation.
It would be instructive if you dropped /data2 out of the picture
entirely and ran the TPC-H benchy using only /data1. I'm sure you'll
see the fragmentation on /data1 in this case.
It seems clear your fragmentation issue is a database management issue,
not an XFS issue. Your answers to my questions should tell us which.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-10 4:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 0:45 fragmentation question Brady Chang
2010-09-08 1:16 ` Brady Chang
2010-09-08 7:10 ` Emmanuel Florac
2010-09-09 14:12 ` Eric Sandeen
2010-09-09 21:59 ` Brady Chang
2010-09-09 22:06 ` Eric Sandeen
2010-09-09 23:41 ` Brady Chang
2010-09-10 3:23 ` Stan Hoeppner
2010-09-10 4:57 ` Stan Hoeppner [this message]
2010-09-09 23:44 ` Brady Chang
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=4C89BAC0.4000607@hardwarefreak.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox