public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu AVILA <mathieu.avila@opencubetech.com>
To: xfs@oss.sgi.com
Subject: Re: extremely slow write performance plaintext
Date: Tue, 25 Jan 2011 10:48:35 +0100	[thread overview]
Message-ID: <4D3E9C73.6090508@opencubetech.com> (raw)
In-Reply-To: <201101250721.14716@zmi.at>


[-- Attachment #1.1: Type: text/plain, Size: 1305 bytes --]

Le 25/01/2011 07:21, Michael Monnerie a écrit :
> On Dienstag, 18. Januar 2011 Cory Coager wrote:
>> Also, I want to stress that I am only having performance issues with
>> one logical volume, the others seem fine.
> You're getting 40MB/s write speed and says that's fine? I get more
> performance from a single SATA desktop drive. Your setup seems to suck
> extremely somewhere.
>
> It already starts with your dd speed. I started it on a virtualized VM
> on an old, overloaded server and get:
>
> # dd if=/dev/zero of=test.dd bs=1k count=1M
> 1048576+0 Datensätze ein
> 1048576+0 Datensätze aus
> 1073741824 Bytes (1,1 GB) kopiert, 10,9992 s, 97,6 MB/s
>

I would say this is melted with cache hit, isn't it ? (although I agree 
it depends on the server's memory dedicated to FS cache)

A real cache hit on a real server would give me at least 500 MB/s 
(actually I get something around 1 GB/s)
When it starts to be disk-constrained, on a standard SATA disk, I get 
from 75 MB/s to 140 MB/s depending on the position of the AG I hit.


-- 
*Mathieu Avila*
IT & Integration Engineer
mathieu.avila@opencubetech.com

OpenCube Technologies http://www.opencubetech.com
Parc Technologique du Canal, 9 avenue de l'Europe
31520 Ramonville St Agne - FRANCE
Tel. : +33 (0) 561 285 606 - Fax : +33 (0) 561 285 635

[-- Attachment #1.2: Type: text/html, Size: 2120 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:[~2011-01-25  9:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 21:22 extremely slow write performance plaintext Cory Coager
2011-01-13 22:35 ` Emmanuel Florac
2011-01-14  0:17   ` Cory Coager
2011-01-14 19:51     ` Stan Hoeppner
2011-01-14 20:48       ` Cory Coager
2011-01-14 22:02         ` Stan Hoeppner
2011-01-18 14:16           ` Cory Coager
2011-01-19  9:59             ` Stan Hoeppner
2011-01-25 14:22               ` Cory Coager
2011-01-25  6:21             ` Michael Monnerie
2011-01-25  9:48               ` Mathieu AVILA [this message]
2011-01-25 14:25                 ` Cory Coager
2011-01-28  6:22                   ` Michael Monnerie
2011-01-28 13:08                     ` Cory Coager
2011-01-25 14:27               ` Cory Coager

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=4D3E9C73.6090508@opencubetech.com \
    --to=mathieu.avila@opencubetech.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