All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Ondrej Kozina <okozina@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: [PATCH 0/9] dm-crypt patches
Date: Tue, 8 Apr 2014 11:44:17 -0400	[thread overview]
Message-ID: <20140408154416.GB4723@redhat.com> (raw)
In-Reply-To: <534414DD.1040500@redhat.com>

On Tue, Apr 08 2014 at 11:25am -0400,
Ondrej Kozina <okozina@redhat.com> wrote:

> Hi,
> 
> I ran all tests again and with new version and everything passed
> even on raid5 back end, so it's right time to paste here some
> performance results:

Thanks for sharing the results.  The system is a pretty low-end machine,
certainly doesn't showcase the intended configuration (improved CPU
scalability on a system with many cores).

BUT it is a useful data point to have.  Because it reflects that the
improvements are realized even on systems without many cores or AES.

> Requirements:
> ------------
> http://okozina.fedorapeople.org/dmcrypt-tests.tar.xz
> compiled fio package
> 
> Performance tests are based on script in subdirectory 1/ in
> http://okozina.fedorapeople.org/dmcrypt-tests.tar.xz
> 
> The result tables were aggregated from output of following fio command:
> 
> fio --output=log --latency-log=log --bandwidth-log=log \
> --name=global --rw=$3 --size=1G --bsrange=1k-128k \
> --filename=$1 \
> --name=job1 --name=job2 --name=job3 --name=job4 \
> --end_fsync=1
> 
> $1 - test device
> $3 - read/write mode see explanation of TEST NAME column below

How is it that you've extracted these results from the test run?  I'd be
open to rerunning the same on my testbed (1 Intel Xeon E5649 Westmere-EP
with 12 logical cores, AES, and 6 SAS devices for RAID, 1 STEC PCIe SSD)

I could also yield this testbed to you if that'd be easier than you
telling me how to extract the test results.

BTW, it seems odd to me that the tests run all the fsx and dt tests yet
only the FIO tests are what you're reporting.. would save time to just
disable the non-fio tests wouldn't it?

  reply	other threads:[~2014-04-08 15:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-05 18:04 [PATCH 0/9] dm-crypt patches Mikulas Patocka
2014-04-05 18:04 ` [PATCH 1/9] dm-crypt: remove per-cpu structure Mikulas Patocka
2014-04-05 18:05   ` [PATCH 2/9] bio: use kmalloc alignment for bio slab Mikulas Patocka
2014-04-05 18:05     ` [PATCH 3/9] dm-crypt: use per-bio data Mikulas Patocka
2014-04-05 18:06       ` [PATCH 4/9] dm-crypt: use unbound workqueue for request processing Mikulas Patocka
2014-04-05 18:07         ` [PATCH 5/9] dm-crypt: don't allocate pages for a partial request Mikulas Patocka
2014-04-05 18:07           ` [PATCH 6/9] dm-crypt: avoid deadlock in mempools Mikulas Patocka
2014-04-05 18:08             ` [PATCH 7/9] dm-crypt: remove io_pool Mikulas Patocka
2014-04-05 18:08               ` [PATCH 8/9] dm-crypt: offload writes to thread Mikulas Patocka
2014-04-05 18:09                 ` [PATCH 9/9] dm-crypt: sort writes Mikulas Patocka
2014-04-07  1:01 ` [PATCH 0/9] dm-crypt patches Mike Snitzer
2014-04-08 15:25 ` Ondrej Kozina
2014-04-08 15:44   ` Mike Snitzer [this message]
2014-04-09  8:46     ` Ondrej Kozina
2014-04-08 21:29   ` Marian Csontos

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=20140408154416.GB4723@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@redhat.com \
    --cc=okozina@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.