Github user davisp commented on the issue:
https://github.com/apache/couchdb-couch/pull/223
Awesome find. I've definitely been perplexed by the I/O changes since
starting to deploy Couch 2.0 code. This definitely seems to explain both the io
differences and the increase in memory usage.
The original commit even calls this a micro optimization so I'm inclined to
completely remove it rather than make it optional. @kxepal, are you wanting to
see a config option or are the graphs on the ticket convincing enough to just
drop it?
Huge +1 from me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
