How time flies … this is still one of the last remaining issues for 3.0. I’ve
written up a modified version of this idea that I think captures the same basic
spirit as a PR against the couchdb-documentation repo:
https://github.com/apache/couchdb-documentation/pull/464
I tried to document IOQ1
After thinking this through a bit more I propose to do the following:
1) Fully document IOQ1 as the workload management / IO queueing capability in
CouchDB
2) Enable IOQ1 by default
3) Add a global bypass switch so users with big, fast servers can quickly
configure CouchDB to make the most of
Maybe it makes sense to look at the 2.x -> 3.x progression of each of these
individually:
## Compaction
Smoosh replaces an earlier compaction daemon. It can certainly be configured to
use more resources than the old one. Changing the default configuration to a
single channel with no
On 2019-09-12 6:00 a.m., Will Holley wrote:
I defer to those with more operational experience of ken and smoosh but
wouldn't those new subsystems radically impact performance if IOQ is
completely bypassed (assuming ken/smoosh are enabled by default)?
A very good point. I'd be uncomfortable
I defer to those with more operational experience of ken and smoosh but
wouldn't those new subsystems radically impact performance if IOQ is
completely bypassed (assuming ken/smoosh are enabled by default)?
On Wed, 11 Sep 2019 at 22:04, Adam Kocoloski wrote:
> A few months ago a bunch of code
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.
