Date: Sun, 28 Mar 2021 22:21:30 +0200 From: Stefan Esser <se@freebsd.org> To: Andriy Gapon <avg@FreeBSD.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Strange behavior after running under high load Message-ID: <c64447e2-4ed4-a948-e15a-efcd66c271a9@freebsd.org> In-Reply-To: <e8398b06-de30-63a8-94b1-a336ed32ed27@FreeBSD.org> References: <58bea0f0-5c3d-4263-ebee-f939a7e169e9@freebsd.org> <e8398b06-de30-63a8-94b1-a336ed32ed27@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --HXyJ655E7viEVZgHwwqwiV0njfOct2N8o Content-Type: multipart/mixed; boundary="hmtZoen9R5nym1vFwn9dESdAzveeZWJ8Q"; protected-headers="v1" From: Stefan Esser <se@freebsd.org> To: Andriy Gapon <avg@FreeBSD.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Message-ID: <c64447e2-4ed4-a948-e15a-efcd66c271a9@freebsd.org> Subject: Re: Strange behavior after running under high load References: <58bea0f0-5c3d-4263-ebee-f939a7e169e9@freebsd.org> <e8398b06-de30-63a8-94b1-a336ed32ed27@FreeBSD.org> In-Reply-To: <e8398b06-de30-63a8-94b1-a336ed32ed27@FreeBSD.org> --hmtZoen9R5nym1vFwn9dESdAzveeZWJ8Q Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable Am 28.03.21 um 17:44 schrieb Andriy Gapon: > On 28/03/2021 17:39, Stefan Esser wrote: >> After a period of high load, my now idle system needs 4 to 10 seconds = to >> run any trivial command - even after 20 minutes of no load ... >> >> >> I have run some Monte-Carlo simulations for a few hours, with initiall= y 35 >> processes running in parallel for some 10 seconds each. >=20 > I saw somewhat similar symptoms with 13-CURRENT some time ago. > To me it looked like even small kernel memory allocations took a very l= ong time. > But it was hard to properly diagnose that as my favorite tool, dtrace, = was also > affected by the same problem. That could have been the case - but I had to reboot to recover the system= =2E I had let it sit idle fpr a few hours and the last "time uptime" before the reboot took 15 second real time to complete. Response from within the shell (e.g. "echo *") was instantaneous, though.= I tried to trace the program execution of "uptime" with truss and found, that the loading of shared libraries proceeded at about one or two per second until all were attached and then the program quickly printed the expected results. I could probably recreate the issue by running the same set of programs that triggered it a few hours ago, but this is a production system and I need it to be operational through the week ... Regards, STefan --hmtZoen9R5nym1vFwn9dESdAzveeZWJ8Q-- --HXyJ655E7viEVZgHwwqwiV0njfOct2N8o Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmBg5UoFAwAAAAAACgkQR+u171r99URP bAf+PACjMW3eihheMoyKzVltIAAXSlMhUGrKvRPBtMioi4IdQxtfq/Hg0ES+MCaRfqH6axrJWNXX tMkTSJ5g6mn/unABsI/eflDTnQ8LHKh4hHmKz0dl81D5QHqT2V4IBwAZjKOSP/BBh5+GF+OExTFR J+ty6z0P2cfz24RKllKzvXPHPjXJa1KMRfbhcZVpddrjCBxGaV45bUCSu5ZhBuScn6OtbLDrik2U elokyDM4d6MGv8wCwhHzwt4G0FY93UzqKraNFosxJIneugezAK8GLgg2df9s3DhzkhqmNIX/UaCy Vu9CYqJXO6n07MIwqkuD6OaU9GGtjeGwmD7WklgWVw== =WFzl -----END PGP SIGNATURE----- --HXyJ655E7viEVZgHwwqwiV0njfOct2N8o--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c64447e2-4ed4-a948-e15a-efcd66c271a9>