From: qiaonuohan <qiaonuohan@cn.fujitsu.com>
To: "\"Zhou, Wenjian/周文?\"" <zhouwj-fnst@cn.fujitsu.com>
Cc: "kernel@kyup.com >> Nikolay Borisov" <kernel@kyup.com>,
Atsushi Kumagai <ats-kumagai@wm.jp.nec.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Subject: Re: [PATCH] makedumpfile: Improve performance for parallel compression with zlib.
Date: Thu, 22 Oct 2015 12:07:14 +0800 [thread overview]
Message-ID: <562860F2.4020109@cn.fujitsu.com> (raw)
In-Reply-To: <562853CE.9000208@cn.fujitsu.com>
Hello Zhou,
The performance improvement shows great according to your data. However,
the data is not that enough to show the change of common use.
Since the amount of 0/1 in a page will cause the vary of time used for
compression, I would like you get more benchmark on different core with
different amount of 0/1.
On 10/22/2015 11:11 AM, "Zhou, Wenjian/周文?" wrote:
> Hello Kumagai,
>
> I test it, and it works well. The following is the results.
>
> in virtual machine(memory 2G):
> with empty memory:
> version | num-threads | time(sec)
> ----------------+---------------+-------------
> devel | 0 | 12.76
> devel | 1 | 19.29
> devel | 2 | 11.56
> + this patch | 0 | 12.85
> + this patch | 1 | 5.61
> + this patch | 2 | 2.68
>
> with full memory:
full memory means memory is occupied by 1, without 0?
> version | num-threads | time(sec)
> ----------------+---------------+-------------
> devel | 0 | 51.18
> devel | 1 | 57.82
> devel | 2 | 41.54
> + this patch | 0 | 49.25
> + this patch | 1 | 44.80
> + this patch | 2 | 33.87
>
>
> in real machine(memory 16G):
> with empty memory:
> version | num-threads | time(sec)
> ----------------+---------------+-------------
> devel | 0 | 86.12
> devel | 1 | 222.37
> devel | 8 | 81.50
> devel | 16 | 98.44
> + this patch | 0 | 86.07
> + this patch | 1 | 84.33
> + this patch | 8 | 14.95
> + this patch | 16 | 13.96
>
> with full memory:
> version | num-threads | time(sec)
> ----------------+---------------+-------------
> devel | 0 | 540.89
> devel | 1 | 715.25
> devel | 8 | 132.54
> devel | 16 | 112.89
> + this patch | 0 | 542.79
> + this patch | 1 | 538.22
> + this patch | 8 | 108.28
> + this patch | 16 | 107.83
>
--
Regards
Qiao Nuohan
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2015-10-22 4:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 5:24 [PATCH] makedumpfile: Improve performance for parallel compression with zlib Atsushi Kumagai
2015-10-22 3:11 ` "Zhou, Wenjian/周文?"
2015-10-22 4:07 ` qiaonuohan [this message]
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=562860F2.4020109@cn.fujitsu.com \
--to=qiaonuohan@cn.fujitsu.com \
--cc=ats-kumagai@wm.jp.nec.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kernel@kyup.com \
--cc=kexec@lists.infradead.org \
--cc=zhouwj-fnst@cn.fujitsu.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.