All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Keech <rkeech@redhat.com>
To: "Nicholas C. Strugnell" <nstrug@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>, consult-list@redhat.com
Subject: Re: [Consult-list] Re: dm-multipath has great	throughput but we'd like more!
Date: Thu, 18 May 2006 20:28:17 +1000	[thread overview]
Message-ID: <446C4C41.2030705@redhat.com> (raw)
In-Reply-To: <1147945356.3183.39.camel@nstrug.surrey.redhat.com>


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

Nicholas C. Strugnell wrote:

>On Thu, 2006-05-18 at 10:04 +0200, Nicholas C. Strugnell wrote: 
>  
>
>>On Thu, 2006-05-18 at 08:44 +0100, Bob Gautier wrote:
>>    
>>
>>>On Thu, 2006-05-18 at 02:25 -0500, Jonathan E Brassow wrote:
>>>      
>>>
>>>>The system bus isn't a limiting factor is it?  64-bit PCI-X will get 
>>>>8.5 GB/s (plenty), but 32-bit PCI 33MHz got 133MB/s.
>>>>
>>>>Can your disks sustain that much bandwidth? 10 striped drives might get 
>>>>better than 200MB/s if done right, I suppose.
>>>>
>>>>        
>>>>
>
>  
>
>>It might make sense to test raw writes to a device with dd and see if
>>that gets comparable performance figures - I'll just try that myself
>>actually.
>>    
>>
>
>write throughput to EVA 8000 (8GB write cache), host DL380 with 2x2Gb/s
>HBAs, 2GB RAM
>
>testing 4GB files:
>
>on filesystems: bonnie++ -d /mnt/tmp -s 4g -f -n 0 -u root
>
>ext3: 129MB/s sd=0.43
>  
>
I presume this is with journal=ordered.  Try with journel=writeback.  
I've seen benchmarks which suggest it can be close to the speed of ext2.

-- 
Red Hat Home
www.redhat.com.au <http://www.redhat.com>

	
	
	
*Richard Keech*
Chief Technology Architect
Red Hat Asia-Pacific
email: rkeech@redhat.com <mailto:rkeech@redhat.com>
mobile: +61 419 036 463
	
	Level 50, 120 Collins Street
Melbourne VIC  3000
phone: +61 3 9225 5258
fax: +61 3 9225 5050
support: 1800 733 428
	

	
	
	


[-- Attachment #1.2.1: Type: text/html, Size: 3687 bytes --]

[-- Attachment #1.2.2: logo_rh_home.png --]
[-- Type: image/png, Size: 1266 bytes --]

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



  reply	other threads:[~2006-05-18 10:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18  7:05 dm-multipath has great throughput but we'd like more! Bob Gautier
2006-05-18  7:19 ` [Consult-list] " Bob Gautier
2006-05-18  7:27   ` Luca Berra
2006-05-18  7:36     ` Jonathan E Brassow
2006-05-18  7:44       ` Luca Berra
2006-05-18  7:25 ` Jonathan E Brassow
2006-05-18  7:44   ` Bob Gautier
2006-05-18  7:55     ` Jonathan E Brassow
2006-05-18  7:59     ` Luca Berra
2006-05-18  8:04     ` [Consult-list] " Nicholas C. Strugnell
2006-05-18  9:42       ` Nicholas C. Strugnell
2006-05-18 10:28         ` Richard Keech [this message]
2006-05-22 15:31         ` Ed Wilts
2006-05-18 20:28     ` Steve Lord
2006-05-18 17:00 ` [Consult-list] " Rod Nayfield

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=446C4C41.2030705@redhat.com \
    --to=rkeech@redhat.com \
    --cc=consult-list@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=nstrug@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.