Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Freebsd-hackers, I'm experiencing very strange situation on my lab system which is E3-1220v2, 8GiB of RAM and 850 EVO SATA SSD (with single ZFS pool). It runs CURRENT r341157. Kernel is built *without* INVARIANTS and other heavy debug aids. Everything works great — but compilation.

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Lev, Saturday, December 8, 2018, 2:13:03 PM, you wrote: > I've checked all "standard" places — CPU is not throttling, SSD looks > perfectly Ok according to SMART and there is no complains from AHCI driver > about timeouts and such, system doesn't start to use swap. ZFS ARC was checked

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Waitman Gobble
‐‐‐ Original Message ‐‐‐ On Saturday, December 8, 2018 8:18 AM, Lev Serebryakov wrote: > Hello Lev, > > Saturday, December 8, 2018, 2:13:03 PM, you wrote: > > > Another strange thing I noticed: when system is in such state, "top -SH" > > shows that sometimes very low-profile processes,

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Lev, Saturday, December 8, 2018, 2:13:03 PM, you wrote: > Another strange thing I noticed: when system is in such state, "top -SH" > shows that sometimes very low-profile processes, like clock software > interrupt (!) could consume large amount of CPU for short periods time. When >

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Mateusz, Saturday, December 8, 2018, 5:27:42 PM, you wrote: >> Looks like each next compiler invocation is slower and more stressful than >> previous one. > Is this a fresh install? Almost fresh. It was installed from some rather fresh 13 snapshot and then upgraded to r341157 and custom

ZFS sends TIRMs to agressively? (Was: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system)

2018-12-08 Thread Lev Serebryakov
Hello Lev, Saturday, December 8, 2018, 7:58:37 PM, you wrote: >> Can you please narrow the problem down to a specific kernel revision? > I'm still not sure it is software or hardware problem. Looks like Samsung 850 EVO doesn't like TRIMs sent by ZFS (and I've thought it is good SSD,

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Lev, Saturday, December 8, 2018, 2:13:03 PM, you wrote: > Even when build is single-job, system becomes unresponsive. With > 4-job build running it could takes up to minute to switch screen's windows! And even with 1-job kernel build upsmon's connection to remote upsd flickers!

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Lev Serebryakov
Hello Eugene, Saturday, December 8, 2018, 4:27:13 PM, you wrote: >> I'm completely lost. Is it problem of software? Hardware? If it is >> hardware problem what should I blame? > Try using different kern.timecounter.hardware and/or kern.eventtimer.timer > but first try

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Mateusz Guzik
On 12/8/18, Lev Serebryakov wrote: > Hello Lev, > > Saturday, December 8, 2018, 2:13:03 PM, you wrote: > > >> Even when build is single-job, system becomes unresponsive. With >> 4-job build running it could takes up to minute to switch screen's >> windows! > And even with 1-job kernel build

Re: Painfully slow compilation (read: "make buildworld buildkernel") on not-so-weak system

2018-12-08 Thread Eugene Grosbein
08.12.2018 18:13, Lev Serebryakov wrote: > I'm completely lost. Is it problem of software? Hardware? If it is > hardware problem what should I blame? Try using different kern.timecounter.hardware and/or kern.eventtimer.timer but first try kern.eventtimer.periodic=1 instead of default 0. If

nda(4) does not work (reliably) in VMware Workstation

2018-12-08 Thread Yuri Pankov
Hi, Running -HEAD in VMware Workstation 15.0.2 VM. Trying to use nda(4) instead of nvd(4) shows the following list of errors, and eventually panics: https://people.freebsd.org/~yuripv/nda1.png https://people.freebsd.org/~yuripv/nda2.png nvd(4) works without issues in this VM. nda(4) works as