Re: Benchmarking kernel, userland and Xenocara build processes

Hi, and thanks for the input! I now (re)understand the reason to compiling the kernel, the userland and Xenocara in a single-thread fashion is obviously the correct way, at least when it comes to doing things properly, minimizing the potential for anything breaking down. That said, I personal

Re: Benchmarking kernel, userland and Xenocara build processes

On Mon, Oct 29, 2018 at 08:11:03AM +0200, Jyri Hovila [Turvamies.fi] wrote: > Hi, > > just for the record, and to inform others who may still be at loss regarding > this matter: when compiling stuff (particularly Big Stuff, such as the > userland) on an OpenBSD machine with several CPU cores, it

Re: Benchmarking kernel, userland and Xenocara build processes

Hi, just for the record, and to inform others who may still be at loss regarding this matter: when compiling stuff (particularly Big Stuff, such as the userland) on an OpenBSD machine with several CPU cores, it's important to pass the '-j ' argument to the make command, in order to benefit fro

Re: Benchmarking kernel, userland and Xenocara build processes

Hi again, to elaborate a bit, the reason I'm interested in getting more detailed benchmark results for the build processes is that I've noticed there are many situations where servers with less hardware resources (CPU cores and RAM in particular) often seem to finish the builds quite a lot fast

Benchmarking kernel, userland and Xenocara build processes

Hi! I have a handful of OpenBSD (CURRENT) instances, running on different VPS and full iron platforms. Since I use CURRENT, keeping up to date means I have the opportunity to watch and compare the build process durations of the kernel, the userland, and Xenocara. For now, I've simply clocked