qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, ehabkost@redhat.com, stefanha@gmail.com,
	mreitz@redhat.com, crosa@redhat.com, den@openvz.org,
	jsnow@redhat.com
Subject: Re: ping Re: [PATCH for-5.0 v2 0/3] benchmark util
Date: Sat, 8 Feb 2020 13:36:28 +0300	[thread overview]
Message-ID: <fca8ced2-b3c6-74db-0d70-11ac3304b273@virtuozzo.com> (raw)
In-Reply-To: <e1efd3d2-b623-292b-67a9-e3cdd479f104@virtuozzo.com>

pingg..

Hi! Could it be merged at all?

20.01.2020 12:10, Vladimir Sementsov-Ogievskiy wrote:
> ping
> 
> 26.11.2019 18:48, Vladimir Sementsov-Ogievskiy wrote:
>> Hi all!
>>
>> Here is simple benchmarking utility, to generate performance
>> comparison tables, like the following:
>>
>> ----------  -------------  -------------  -------------
>>              backup-1       backup-2       mirror
>> ssd -> ssd  0.43 +- 0.00   4.48 +- 0.06   4.38 +- 0.02
>> ssd -> hdd  10.60 +- 0.08  10.69 +- 0.18  10.57 +- 0.05
>> ssd -> nbd  33.81 +- 0.37  10.67 +- 0.17  10.07 +- 0.07
>> ----------  -------------  -------------  -------------
>>
>> This is a v2, as v1 was inside
>>   "[RFC 00/24] backup performance: block_status + async"
>>
>> I'll use this benchmark in other series, hope someone
>> will like it.
>>
>> Vladimir Sementsov-Ogievskiy (3):
>>    python: add simplebench.py
>>    python: add qemu/bench_block_job.py
>>    python: add example usage of simplebench
>>
>>   python/bench-example.py        |  80 +++++++++++++++++++++
>>   python/qemu/bench_block_job.py | 115 +++++++++++++++++++++++++++++
>>   python/simplebench.py          | 128 +++++++++++++++++++++++++++++++++
>>   3 files changed, 323 insertions(+)
>>   create mode 100644 python/bench-example.py
>>   create mode 100755 python/qemu/bench_block_job.py
>>   create mode 100644 python/simplebench.py
>>
> 
> 


-- 
Best regards,
Vladimir


  reply	other threads:[~2020-02-08 10:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 15:48 [PATCH for-5.0 v2 0/3] benchmark util Vladimir Sementsov-Ogievskiy
2019-11-26 15:48 ` [PATCH for-5.0 v2 1/3] python: add simplebench.py Vladimir Sementsov-Ogievskiy
2019-11-26 15:48 ` [PATCH for-5.0 v2 2/3] python: add qemu/bench_block_job.py Vladimir Sementsov-Ogievskiy
2019-11-26 15:48 ` [PATCH for-5.0 v2 3/3] python: add example usage of simplebench Vladimir Sementsov-Ogievskiy
2019-11-27 19:58 ` [PATCH for-5.0 v2 0/3] benchmark util Aleksandar Markovic
2019-11-27 20:22   ` Vladimir Sementsov-Ogievskiy
2019-12-06 19:43 ` Cleber Rosa
2019-12-06 20:00   ` Vladimir Sementsov-Ogievskiy
2019-12-19  8:22 ` Vladimir Sementsov-Ogievskiy
2020-01-20  9:10 ` ping " Vladimir Sementsov-Ogievskiy
2020-02-08 10:36   ` Vladimir Sementsov-Ogievskiy [this message]
2020-02-27 13:18     ` Vladimir Sementsov-Ogievskiy
2020-02-27 20:09       ` Eduardo Habkost
2020-02-28  6:24         ` Vladimir Sementsov-Ogievskiy

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=fca8ced2-b3c6-74db-0d70-11ac3304b273@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=crosa@redhat.com \
    --cc=den@openvz.org \
    --cc=ehabkost@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).