Date: Mon, 5 Apr 2021 16:03:12 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Santiago Martinez <sm@codenetworks.net>, freebsd-current@freebsd.org Subject: Re: freebsd 13 ryzen micro stutter Message-ID: <1de5d976-a82b-eb93-7754-8c739571c242@FreeBSD.org> In-Reply-To: <9638abfe-fd9e-6855-b3c7-ee796d1c5ce5@codenetworks.net> References: <d793c8b7-e0e2-e0d9-3ecd-923134d15bf3@twcny.rr.com> <20210323101146.18c9a969@bsd64.grem.de> <ED533759-D326-45D5-8AE2-51CB10763A1E@unrelenting.technology> <677da81d7af9781be6b46c7cba4efd05@riseup.net> <54768f44-c110-d58a-1e7b-61843cde754e@codenetworks.net> <9638abfe-fd9e-6855-b3c7-ee796d1c5ce5@codenetworks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27/03/2021 12:54, Santiago Martinez wrote: > Hi, i have the same output as @Nils B. If i run with steal =2 and dtrace the > micro stutter doesn't happen but as soon as i stop the dtrace script it the > stutters come back again. It seems that DTrace creates some extra CPU load that masks the problem. So, I guess that DTrace produced traces won't have many clues, if any at all. I wonder if KTR tracing would be better in this respect. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1de5d976-a82b-eb93-7754-8c739571c242>