Re: Possible regression in main causing poor performance

On Sep 5, 2023, at 08:58, Cy Schubert <[email protected]> wrote:

> In message <[email protected]>, Cy Schubert writes:
>> In message <[email protected]>, Glen Barber writes:
>>> 
>>> 
>>> On Mon, Aug 28, 2023 at 06:06:09PM -0700, Mark Millard wrote:
>>>> Has any more been learned about this? Is it still an issue?
>>>> =20
>>> 
>>> I rebooted the machine before the ALPHA3 builds with no other changes,
>>> and the overall times for 14.x builds went back to normal.  I do not
>>> like to experiment with builders during a release cycle, but as we are
>>> going to have 15.x snapshots available moving forward, I will not reboot
>>> that machine next week in hopes to get some useful data.
>>> 
>>> If my memory serves correctly, mm@ has a pending ZFS import from
>>> upstream for both main and stable/14 pending.  Whether or not that will
>>> resolve any issue here, I do not know.
>> 
>> Two of my poudriere builder machines have experienced different panics 
>> since the ZFS import two days ago. The problems have been documented on the 
>> -current list.
> 
> Just an update.
> 
> The three pull requests amotin@ pointed to did resolve all my problems. A 
> subsequent update which included the latest ZFS commits worked just as 
> well, without any new regressions. AFAIAC this problem has been resolved.
> 
> The random email corruptions have also been resolved.
> 
> 
> -- 
> Cheers,
> Cy Schubert <[email protected]>
> FreeBSD UNIX:  <[email protected]>   Web:  https://FreeBSD.org
> NTP:           <[email protected]>    Web:  https://nwtime.org
> 
> e^(i*pi)+1=0
> 
> 
> 
> 
> œ9O8

The just-above quoted line looks like a corruption to me.

Otherwise, I'm just reporting more evidence from separate
testing on amd64 . . .

I will say that my separate-install/boot environment 10hr,
6366 port->package poudriere bulk -a prefix test of:

# uname -apKU
FreeBSD amd64-ZFS 15.0-CURRENT FreeBSD 15.0-CURRENT amd64 1500000 #118 main-n265152-f49d6f583e9d-dirty: Mon Sep  4 14:26:56 PDT 2023     root@amd64_ZFS:/usr/obj/BUILDs/main-amd64-nodbg-clang/usr/main-src/amd64.amd64/sys/GENERIC-NODBG amd64 amd64 1500000 1500000

did not show any deadlocks. The only oddity that I've noticed
is the 1 extra message shown in:

. . .
[00:03:25] [32] [00:00:00] Builder starting
[00:03:43] [01] [00:00:18] Finished print/indexinfo | indexinfo-0.3.1: Success
[00:03:43] [01] [00:00:00] Building devel/gettext-runtime | gettext-runtime-0.22_1
[00:05:20] [01] [00:01:37] Finished devel/gettext-runtime | gettext-runtime-0.22_1: Success
23/.p/cleaning/rdeps/gettext-runtime-0.22_1/chemtool-1.6.14_4 copy: open failed: No such file or directory
[00:05:23] [01] [00:00:00] Building devel/gmake | gmake-4.3_2
[00:05:55] [02] [00:02:30] Builder started
. . .

I'm comfortable moving my normal environments forward to include
this latest import of openzfs.

The effort established a separate environment set up for
doing testing of jumping to/past an openzfs import(s) in
main. Too many recent imports have
dangerous-to-the-file-system and/or had deadlocking issues
for me to simply update to include them without first
testing on separate media that does not have to stay
operational.

===
Mark Millard
marklmi at yahoo.com