All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Correia <Ricardo.M.Correia@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] ZFS/DMU benchmarks
Date: Tue, 13 Nov 2007 11:48:38 +0000	[thread overview]
Message-ID: <47398F16.5000504@Sun.COM> (raw)
In-Reply-To: <C882B223-8FE1-4FA1-9885-97BDFD20B1E7@sun.com>

Hi everyone,

Here are some current ZFS/DMU benchmark results that might be of 
interest to you.
These results were obtained on a Sunfire x4500 with these specifications:

- 2 dual-core AMD Opteron processors
- 16 GB main memory
- 48 SATA II HDD (7200 RPM, 500 GB each)
- Solaris 10 update 3
- Userspace DMU from OpenSolaris build 74

The tool used in this particular benchmark was PIOS, which simulates a 
parallel I/O load typically experienced by an OSS. Since PIOS links 
directly with the DMU, it should give a good estimation of the maximum 
throughput of the userspace DMU-OSS. For comparison, you can also see 
the results of running the same PIOS benchmark with normal POSIX I/O on 
the Solaris 10u3 ZFS implementation.

See the attached PDF for the results.

First page provides PIOS throughput information on striped pools with 
10, 24 and 46 disks. uDMU outperforms kernel ZFS with 10 disks, however, 
the kernel ZFS implementation scales better to 24 and 46 disks. 
Surprisingly enough, disabling checksums has a negative impact on the 
throughput with a 10-disk striped pool. This impact can be attributed to 
the differences in the uDMU IO pipeline which are probably causing the 
IOs to not being parallelized when checksumming is disabled. This issue, 
however, should not be hard to fix.

Second page shows the results of running PIOS on RAID-Z, RAID-Z2 and 
mirrored pools. In these configurations, the kernel ZFS currently has a 
better throughput than the userspace DMU.

These results were obtained with only minimal tuning of the DMU (setting 
a maximum cache size and increasing the number of I/O threads). Work is 
already underway to improve the performance of the DMU and we expect to 
see better throughput in the coming months.

Best regards,
Ricardo

-- 
<http://www.sun.com> 	* Ricardo Manuel Correia *

Lustre Engineering Group
*Sun Microsystems, Inc.*
Portugal

Ricardo.M.Correia at Sun.COM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20071113/a7e9a9ee/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Lustre-uDMU.pdf
Type: application/pdf
Size: 66695 bytes
Desc: not available
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20071113/a7e9a9ee/attachment.pdf>

       reply	other threads:[~2007-11-13 11:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C882B223-8FE1-4FA1-9885-97BDFD20B1E7@sun.com>
2007-11-13 11:48 ` Ricardo Correia [this message]
2007-11-14 21:58   ` [Lustre-devel] [Lustre-discuss] ZFS/DMU benchmarks Jody McIntyre
2007-11-15  0:14     ` Jim Garlick
2007-11-20 17:01   ` [Lustre-devel] " Ricardo M. Correia
2007-11-28 14:57     ` [Lustre-devel] ZFS in User Space RS RS

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=47398F16.5000504@Sun.COM \
    --to=ricardo.m.correia@sun.com \
    --cc=lustre-devel@lists.lustre.org \
    /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.