FreeBSD 15 performance benchmarks

Michael Larabel at Phoronix recently conducted and published some performance benchmarks of the new 15.0-RELEASE.

1765384974966.png


Highlights include dominant performance from create threads and memory allocation, but also from Zstd compression and x265 video codec.

Curious misses include iPerf and write performance on OpenZFS. I wonder if UFS2 would've done better.

Overall, not bad considering the differential in investment.
 
Highlights include dominant performance from create threads and memory allocation, but also from Zstd compression and x265 video codec.

glibc's malloc is whack. If Michael would re-run these benchmarks with LD_PRELOAD to tcmalloc Linux would do much better.

Overall pretty disappointing. We used to be pretty equivalent until recently. But as you can see on Phoronix over the last years Linux made several expensive investments that did lead to incremental improvements. Can't believe we are now slower on PyBench.

And all that is on a machine without NUMA.
 
So best performing is 1907.43, FBSD is 1600.25. Delta of 307.18. What does that actually mean? Raw numbers is "about 20%", what is that?

Perf stats are always great to have but I've always had trouble correlating them to real world usage.

I have no doubt that the numbers are accurate for the scenarios, it's the mapping of the scenarios.
 
So best performing is 1907.43, FBSD is 1600.25. Delta of 307.18. What does that actually mean? Raw numbers is "about 20%", what is that?

Perf stats are always great to have but I've always had trouble correlating them to real world usage.

I have no doubt that the numbers are accurate for the scenarios, it's the mapping of the scenarios.

Michael's whole benchmark suite is open source. I found the parts I tried to run reasonably straightforward to use.

He also links to the large tables of raw numbers of his results.
 
  • Like
Reactions: mer
cracauer@ thanks. For me, I've always looked at benchmarks with a grain of salt. I've seen too many that optimize for a cpu/os. I do not think that is what is happening, but I've seen enough in the past to look with interest but not finality.

It always boils down to how does my system feel to me under this load.
 
cracauer@ thanks. For me, I've always looked at benchmarks with a grain of salt. I've seen too many that optimize for a cpu/os. I do not think that is what is happening, but I've seen enough in the past to look with interest but not finality.

Michael strictly does benchmarking with stock OSes and stock machines, no tuning. I'm pretty such that I could improve the Linux results in this run with tcmalloc and setting preemption to none. But I would have to run all that stuff myself.

A networker probably has something to tinker with in the iperf benchmarks with FreeBSD. And as you say, what really matters is how the OS handles things where there is both CPU demand and high I/O at the same time. That is annoying to benchmark.
 
These benchmarks show (only) that without fine tuning, FreeBSD is slower than Ubuntu in some benchmarks, faster in others, and in general a little slower but good enough. But there are so many run-time and compile-time options, and so many different real-world usage scenario, that everything can change in favour of Linux or FreeBSD, if administrators put some effort in fine-tuning the OS and the applications/services. So it can be exciting see a "Formula One" race between OS...
:)


Moreover an OS must be: easy to administer/monitor; secure; reliable; etc.. For example in these benchmarks, Ubuntu is using ext4, while FreeBSD ZFS. The differences in features between the two file systems is so enormous, that raw performances can become not important in certain usage scenario. Or there can be combination of hardware where ZFS is faster.
 
These benchmarks show (only) that without fine tuning, FreeBSD is slower than Ubuntu in some benchmarks, faster in others, and in general a little slower but good enough. But there are so many run-time and compile-time options, and so many different real-world usage scenario, that everything can change in favour of Linux or FreeBSD, if administrators put some effort in fine-tuning the OS and the applications/services. So it can be exciting see a "Formula One" race between OS...

Outside of networking I see more opportunity to tune Ubuntu than FreeBSD for these benchmarks.

Networking is a different matter, we have seen FreeBSD react strongly to some tuning.

There also is the compiler choice which probably is responsible for some of the differences. But you can't compile the Linux kernel with clang (I think) and you can't compile the FreeBSD with gcc anymore (I think). Benchmarking on even terms is hard.
 
Outside of networking I see more opportunity to tune Ubuntu than FreeBSD for these benchmarks.

Networking is a different matter, we have seen FreeBSD react strongly to some tuning.

There also is the compiler choice which probably is responsible for some of the differences. But you can't compile the Linux kernel with clang (I think) and you can't compile the FreeBSD with gcc anymore (I think). Benchmarking on even terms is hard.
You can compile with clang: https://www.kernel.org/doc/html/latest/kbuild/llvm.html
Some distros do offer kernels compiled with clang, but there isn't much difference there, some wins some losses.
 
Back
Top