public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: XFS Test Results Interpretation
Date: Sat, 23 Oct 2010 22:38:25 -0500	[thread overview]
Message-ID: <4CC3AA31.2000101@hardwarefreak.com> (raw)
In-Reply-To: <3C5E029826A0704DB5998577FCFF46F0095A278CBF@dagobah>

Andrew Debenham put forth on 10/23/2010 9:59 PM:
> I am in the process of trying to determine the best parameters to use when creating and mounting an XFS file system on some new hardware we are going to be using.  My company has two separate applications that will be running on the same hardware (but on separate systems).  One application is the PostgreSQL database and the other is a custom application that does writes to many (~1,000) relatively small (~672MB) files concurrently.

Post the detailed hardware specs (server, local RAID or SAN, number of
disks in stripe set, RAID level, etc), and if both applications are
running on the same physical machine or different machines.  Are both
apps writing to the same XFS filesystem or two different filesystems?
Your description of "what is where" was very confusing.

Oh, and Bonnie++ test results are usually useless, as well as IOZone,
etc.  Next time ask before taking the time to run benchmarks and jump
through hoops to get the data onto the list. :)

-- 
Stan

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

  reply	other threads:[~2010-10-24  3:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-24  2:59 XFS Test Results Interpretation Andrew Debenham
2010-10-24  3:38 ` Stan Hoeppner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-10-25 11:17 Andrew Debenham
2010-10-25 11:51 ` Michael Monnerie
2010-10-25 13:42 ` Stan Hoeppner
2010-10-25 14:06   ` Michael Monnerie

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=4CC3AA31.2000101@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