A few months ago a bunch of code landed on master around IO QoS and
prioritization. I think we need to have a conversation about the defaults for
that system and what we want to allow users to enable.
First topic - there are actually two different generations of the IOQ system:
IOQ and IOQ2.
Hi Jan -
Do you happen to have the ticket/link for this?
> I remembered one last deprecation we wanted in 3.0: security tightening,
> which included the deprecation of admin party.
>
Thanks!
Deni
On Mon, Sep 9, 2019 at 2:14 PM Joan Touzet wrote:
> I remembered one last deprecation we wanted
> For me the main question is how much overhead is associated with tracing.
Bellow is a breakdown on cost of various operations
> Can an admin safely configure it to run in production?
I believe it can be used in production if we are careful with filters. We need
to configure prefilter_rules
This looks really good. Just checking are we planning to integrate this for
the 3.x release or 4.x?
On Wed, Sep 11, 2019 at 12:50 AM Paul Davis
wrote:
> +1
>
> On Tue, Sep 10, 2019 at 4:51 PM Adam Kocoloski
> wrote:
> >
> > Yeah, I meant the latter — joining CouchDB’s span information to spans
