Date: Sun, 21 Aug 2016 14:45:05 +0800 From: Erich Dollansky <erichsfreebsdlist@alogt.com> To: Kubilay Kocak <koobs@FreeBSD.org> Cc: freebsd-stable <freebsd-stable@FreeBSD.org> Subject: Re: Benchmarks results for FreeBSD 11 Message-ID: <20160821144505.27c0f55d@X220.alogt.com> In-Reply-To: <af0fefab-69d7-f0a9-3d6d-4a9891d5a156@FreeBSD.org> References: <20160819073422.4292997b@X220.alogt.com> <af0fefab-69d7-f0a9-3d6d-4a9891d5a156@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
Hi, On Sun, 21 Aug 2016 15:21:01 +1000 Kubilay Kocak <koobs@FreeBSD.org> wrote: > On 19/08/2016 9:34 AM, Erich Dollansky wrote: > > > > I am sure that some know of this site: > > > > http://www.phoronix.com/scan.php?page=article&item=2bsd-7linux-bench&num=4 > > > > I wonder about the results for FreeBSD. As I do not have 11 on my > > machines, a stupid question. Are there still some debugging aids > > enabled in 11? > > They're off in those versions, but did note compiler (and compiler > args) differences between within most tests (See attachments) as you > mentioned. > the benchmark then compares the off-the-shelve distributions. > > > I know that some of the results are caused by the use of CLang and > > some of the results test applications/compilers and not operating > > systems. > > gcc/clang tests and defaults in upstream build systems are almost > certainly contributors. At a minimum it would be nice to see an > attempt to standardise (force) compiler args across all OS runs for > the same test, even if this doesn't prove to be perfect. Yes, without, he compares compilers more than operating systems. > > Separating or adding tests for the same tests using non-default > compilers (in particular latest GCC versions from ports) so they match > across OS's would also be valuable. > > At a minimum it would be worth Michael highlighting the differences, > and ideally removing these variables from the tests, even if they > aren't default configurations. Though a test of out of the box > configurations is still valuable, it can serve to muddy the > underlying differences and make them tougher to isolate. He never does this. I have no idea what he wants to achieve with his benchmarking all the while as the results are very difficult to compare with real life workloads. Erichhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160821144505.27c0f55d>