Date: Fri, 11 Feb 2022 13:31:49 +0100 From: Mateusz Piotrowski <0mp@FreeBSD.org> To: Chuck Silvers <chs@FreeBSD.org> Cc: src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-main@FreeBSD.org, dtrace@freebsd.org Subject: Re: git: f339a3ef6369 - main - dtrace: remove unnecessary fflush() Message-ID: <38e73169-d322-4c8f-0781-ac60e67c66da@FreeBSD.org> In-Reply-To: <YgVoVFRM%2B0r0kDcV@spathi.chuq.com> References: <202202100248.21A2mMWw070398@gitrepo.freebsd.org> <50175512-5528-f93f-33cf-90f92f2e41b1@FreeBSD.org> <YgVoVFRM%2B0r0kDcV@spathi.chuq.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/02/2022 20:32, Chuck Silvers wrote: > On Thu, Feb 10, 2022 at 02:36:30PM +0100, Mateusz Piotrowski wrote: >> >> Did you have some specific way to measure the CPU overhead of DTrace here? >> I'm interested in this kind of performance measurements and I wonder if >> anything more sophisticated than observing top(1) was used to test this >> change. Thanks! > I just looked at top and saw that the CPU usage of the dtrace process > dropped from 100% to around 13%. More importantly, when the fflush was > present dtrace would report that millions of output records were being > dropped, and after the fflush was removed then dtrace no longer reported > any dropped output. Thanks! Mateusz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38e73169-d322-4c8f-0781-ac60e67c66da>