Date: Sun, 5 Apr 2015 02:48:39 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Tobias Oberstein <tobias.oberstein@gmail.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Michael Fuckner <michael@fuckner.net>, Jim Harris <jim.harris@gmail.com>, Alan Somers <asomers@freebsd.org> Subject: Re: NVMe performance 4x slower than expected Message-ID: <20150404234839.GM2379@kib.kiev.ua> In-Reply-To: <551FC7B3.80203@gmail.com> References: <CAOtMX2jVwMHSnQfphAF%2Ba2%2Bo7eLp62nHmUo4t%2BEahrXLWReaFQ@mail.gmail.com> <CAJP=Hc-RNVuhPePg7bnpmT4ByzyXs_CNvAs7Oy7ntXjqhZYhCQ@mail.gmail.com> <551C5A82.2090306@gmail.com> <20150401212303.GB2379@kib.kiev.ua> <CAJP=Hc87FMYCrQYGfAtefQ8PLT3WtnvPfPSppp3zRF-0noQR9Q@mail.gmail.com> <551C6B62.7080205@gmail.com> <CAJP=Hc_6BFpoWqkSRyZaxsN1Zn=-D14CXOQjMb4zjnZRKhMb-g@mail.gmail.com> <551D4E5F.9090400@gmail.com> <20150402221029.GE2379@kib.kiev.ua> <551FC7B3.80203@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 04, 2015 at 01:14:59PM +0200, Tobias Oberstein wrote: > >> I was advised (off list) to run tests against a pure ramdisk. > >> > >> Here are results from a single socket E3: > >> > >> https://github.com/oberstet/scratchbox/blob/master/freebsd/cruncher/results/freebsd_ramdisk.md#xeon-e3-machine > >> > >> and here are results for the 48 core box > >> > >> https://github.com/oberstet/scratchbox/blob/master/freebsd/cruncher/results/freebsd_ramdisk.md#48-core-big-machine > >> > >> Performance with this box is 1/10 on this test compared to single socket E3! > >> > >> Something is severely wrong. It seems, there might be multiple issues > >> (not only NVMe). And this is after already running with 3 patches to > >> make it even boot. > > The speed of dd already looks wrong. > > Yes. Try some simple checks for the performance anomalies. E.g., verify the raw memory bandwidth, check that it is in the expected range. Quick search popped up the following tool, e.g.: https://zsmith.co/bandwidth.html > > > > > Check the CPU frequency settings in BIOS, and check what sysctl dev.cpu > > reports. Ensure that cpufreq.ko is loaded from loader.conf. > > It's loaded now, and CPU clock is at maximum: dev.cpu.0.freq: 3000 > > Unfortuanetly, performance (randomio/fio) did not change ..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150404234839.GM2379>