Date: Fri, 19 Feb 2016 14:14:24 -0500 From: Tom Curry <thomasrcurry@gmail.com> To: "Michael W. Lucas" <mwlucas@michaelwlucas.com> Cc: fs@freebsd.org Subject: Re: dtracing ZFS on FreeBSD Message-ID: <CAGtEZUCnXDbKb6ZpXbV6Mz=1x=Z6syzUBdvuxRs-3Ch3k5m1sw@mail.gmail.com> In-Reply-To: <20160219190753.GA47502@mail.michaelwlucas.com> References: <20160219180716.GA46881@mail.michaelwlucas.com> <CAGtEZUB31Uwk1Ge_DPB_scP6Sw6D4s-w6WgbXr_k_zDL0DB7dQ@mail.gmail.com> <20160219190753.GA47502@mail.michaelwlucas.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 19, 2016 at 2:07 PM, Michael W. Lucas <mwlucas@michaelwlucas.com > wrote: > On Fri, Feb 19, 2016 at 01:51:21PM -0500, Tom Curry wrote: > > For the variable drops you could try increasing the buffer size, I > know > > I ran into this when I was tracing something very noisy and it > > definitely helped. > > #pragma D option bufsize=1m > > Cranking it up to the limit of 16m helps, thank you. > > But the problem still appears during load, just not as often. > > Any other suggestions, anyone? > > One other thing to try in concert with the larger buffer, #pragma D option bufpolicy=ring In theory I would expect it not to drop, but the window of tracing would be smaller.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGtEZUCnXDbKb6ZpXbV6Mz=1x=Z6syzUBdvuxRs-3Ch3k5m1sw>