public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Richard Ems <richard.ems@cape-horn-eng.com>
Subject: Re: cannot defrag volume, fragmentation factor 21.73%
Date: Fri, 22 Oct 2010 23:02:38 +0200	[thread overview]
Message-ID: <201010222302.39061@zmi.at> (raw)
In-Reply-To: <4CC1638B.4070807@cape-horn-eng.com>


[-- Attachment #1.1: Type: Text/Plain, Size: 1347 bytes --]

On Freitag, 22. Oktober 2010 Richard Ems wrote:
> But, at which numbers should I look at before starting a defrag then?

Watch the performance of your application. Record answer times with 
munin or something, and if you ever "feel" it's too slow, look at the 
recorded numbers again to see if your feelings fit the measurements. 
Don't be paranoid about fragmentation. The more people access a server 
at a time, the less important fragmentation is. 

If you got 100 people streaming 100 perfect defragmented files, you 
still got an access pattern that needs to move the disk head to 100 
different positions all the time. If your single disk can't do that many 
I/O's, build up a RAID, or get faster disks (10kprm, 15krpm, SSD).

Defrag is more for single threaded I/O workloads, where one stream at a 
time has to be read/written. Therefore it helps on a Windows PC more 
than on a server. Only use defrag if you really have lots of chunks per 
file.

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31

****** Radiointerview zum Thema Spam ******
http://www.it-podcast.at/archiv.html#podcast-100716

// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

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

      reply	other threads:[~2010-10-22 21:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18 12:09 cannot defrag volume, fragmentation factor 21.73% Richard Ems
2010-10-18 12:39 ` Michael Monnerie
2010-10-18 13:46   ` Richard Ems
2010-10-18 17:58     ` Michael Monnerie
2010-10-18 20:16 ` Stan Hoeppner
2010-10-18 23:10 ` Dave Chinner
2010-10-19  9:37   ` Richard Ems
2010-10-22 10:12   ` Richard Ems
2010-10-22 21:02     ` Michael Monnerie [this message]

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=201010222302.39061@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --cc=richard.ems@cape-horn-eng.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