linux-kernel - RE: Mainline kernel OLTP performance update

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <D7C42C27E6CB1E4D8CBDF2F81EA92A260345D49022@azsmsx501.amr.corp.intel.com>
Date:	Wed, 6 May 2009 11:05:04 -0700
From:	"Styner, Douglas W" <douglas.w.styner@...el.com>
To:	"Wilcox, Matthew R" <matthew.r.wilcox@...el.com>,
	Anirban Chakraborty <anirban.chakraborty@...gic.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:	"Tripathi, Sharad C" <sharad.c.tripathi@...el.com>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"Kleen, Andi" <andi.kleen@...el.com>,
	"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
	"Ma, Chinang" <chinang.ma@...el.com>,
	"Wang, Peter Xihong" <peter.xihong.wang@...el.com>,
	"Nueckel, Hubert" <hubert.nueckel@...el.com>,
	"Recalde, Luis F" <luis.f.recalde@...el.com>,
	"Nelson, Doug" <doug.nelson@...el.com>,
	"Cheng, Wu-sun" <wu-sun.cheng@...el.com>,
	"Prickett, Terry O" <terry.o.prickett@...el.com>,
	"Shunmuganathan, Rajalakshmi" <rajalakshmi.shunmuganathan@...el.com>,
	"Garg, Anil K" <anil.k.garg@...el.com>,
	"Chilukuri, Harita" <harita.chilukuri@...el.com>,
	"chris.mason@...cle.com" <chris.mason@...cle.com>
Subject: RE: Mainline kernel OLTP performance update

Wilcox, Matthew R writes:
>I'm not sure that Orion is going to give useful results in your hardware
>setup.  I suspect you don't have enough spindles to get the IO rates that
>are required to see the problem.  How about doing lots of contiguous I/O
>instead?  Something as simple as:
>
>for i in sda sdb sdc (repeat ad nauseam); do \
>	dd if=/dev/$i of=/dev/null bs=4k iflag=direct & \
>done
>

A better workload emulator would be to use FIO to generate ~60%/40% reads/writes with ~90-95% random i/o using 2k blksize.  There is some sequential writing in our workload but only to a log file and there is not much activity there.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/