Benchmarks results for FreeBSD 11

[Chris]

On 29 August 2016 at 09:30, Fernando Herrero Carrón <elferdo at gmail.com> wrote:
> 2016-08-29 3:04 GMT+02:00 K. Macy <kmacy at freebsd.org>:
>
>> > I'm writing from my cellphone away from my computer, so take this with a
>> > grain of salt:
>> >
>> > -L/usr/local/llvm38/lib
>>
>> You're missing the point. If your webserver crashes every other day,
>> the fact that you can run a batch job to restart it doesn't make it
>> OK.
>>
>>
> Fair enough, I misunderstood the point as "clang, even from ports, cannot
> do omp at all [from a shell]".
>
>
>> [...] Requiring additional tweaking to build on FreeBSD
>> or requiring users to install gcc is kind of underwhelming.
>>
>
> Isn't that precisely what the ports infrastructure is supposed to do? What
> about compiler.mk? If it can provide an extra library-dirs argument to the
> port's configure then we're not that bad. And still I agree, this is far
> from an ideal situation, and we speaking about finding a library, we have
> still not touched having clang use the LLVM linker...
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"

I have not looked at the article yet. but yes if one compiles FreeBSD
ports using a default make.conf (empty file) then the ports will not
be built optimised.
I dont go all out on optimisation like some people do but I consider
basic optimisation to be a modern version of gcc combined with the cpu
native flag.  Which will auto detect the processor used and add the
right flags correctly.  I dont fiddle with -O2 -O3 etc.

However there is a flipside to this on performance, ubuntu packages by
default are now built with PIE, BIND_NOW, SMACK, RELRO etc.  These
will all slow down performance but are modern expected hardening.
FreeBSD I think still does not do this by default? and as such ubuntu
is managing to beat FreeBSD whilst also adding exploit mitigations
which is impressive.

It is a real shame the default ports compile and base has not been
looked into but instead it all has been kept on conservative approach
which is no exploit protection and to compile for the lowest
denominator like a 486 cpu.  Hardened bsd has done some good work on
this but I see they were forced to fork away because their changes
were rejected on the base system.

As a final note I assumed clang no longer has a noticeable
disadvantage vs gcc, if it does then that's bad news for the base
files.

If I Am wrong on the above please feel free to correct me.

Chris