[GitHub] couchdb-couch pull request #223: Remove 8kB read-ahead from couch_file
GitHub user nickva opened a pull request: https://github.com/apache/couchdb-couch/pull/223 Remove 8kB read-ahead from couch_file In production it showed an increased input Erlang IO and increased binary memory usage. See attached file in Jira ticket: COUCHDB-3284 You can merge this pull request into a Git repository by running: $ git pull https://github.com/cloudant/couchdb-couch couchdb-3284 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-couch/pull/223.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #223 commit d52a5335d930d11ade4953c8576d22f55872ff6f Author: Nick VatamaniucDate: 2017-01-27T17:04:01Z Remove 8kB read-ahead from couch_file In production it showed an increased input Erlang IO and increased binary memory usage. See attached file in Jira ticket: COUCHDB-3284 --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-3284) 8Kb read-ahead in couch_file causes extra IO and binary memory usage
[ https://issues.apache.org/jira/browse/COUCHDB-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843544#comment-15843544 ] ASF GitHub Bot commented on COUCHDB-3284: - GitHub user nickva opened a pull request: https://github.com/apache/couchdb-couch/pull/223 Remove 8kB read-ahead from couch_file In production it showed an increased input Erlang IO and increased binary memory usage. See attached file in Jira ticket: COUCHDB-3284 You can merge this pull request into a Git repository by running: $ git pull https://github.com/cloudant/couchdb-couch couchdb-3284 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-couch/pull/223.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #223 commit d52a5335d930d11ade4953c8576d22f55872ff6f Author: Nick VatamaniucDate: 2017-01-27T17:04:01Z Remove 8kB read-ahead from couch_file In production it showed an increased input Erlang IO and increased binary memory usage. See attached file in Jira ticket: COUCHDB-3284 > 8Kb read-ahead in couch_file causes extra IO and binary memory usage > > > Key: COUCHDB-3284 > URL: https://issues.apache.org/jira/browse/COUCHDB-3284 > Project: CouchDB > Issue Type: Bug > Components: Database Core >Affects Versions: 2.0.0 >Reporter: Nick Vatamaniuc > Attachments: jira_io_increased.png > > > 8Kb read-ahead logic in couch_file seems to cause extra input IO thrashing, > binary memory usage but doesn't speed-up -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-3284) 8Kb read-ahead in couch_file causes extra IO and binary memory usage
[ https://issues.apache.org/jira/browse/COUCHDB-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843539#comment-15843539 ] Nick Vatamaniuc commented on COUCHDB-3284: -- Attached performance graphs showing increased IO usage and increased binary memory usage. Those go away after disabling 8kb read-ahead logic > 8Kb read-ahead in couch_file causes extra IO and binary memory usage > > > Key: COUCHDB-3284 > URL: https://issues.apache.org/jira/browse/COUCHDB-3284 > Project: CouchDB > Issue Type: Bug > Components: Database Core >Affects Versions: 2.0.0 >Reporter: Nick Vatamaniuc > Attachments: jira_io_increased.png > > > 8Kb read-ahead logic in couch_file seems to cause extra input IO thrashing, > binary memory usage but doesn't speed-up -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-3284) 8Kb read-ahead in couch_file causes extra IO and binary memory usage
Nick Vatamaniuc created COUCHDB-3284: Summary: 8Kb read-ahead in couch_file causes extra IO and binary memory usage Key: COUCHDB-3284 URL: https://issues.apache.org/jira/browse/COUCHDB-3284 Project: CouchDB Issue Type: Bug Reporter: Nick Vatamaniuc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-3013) Empty selector and empty $and selector not returning same results
[ https://issues.apache.org/jira/browse/COUCHDB-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843376#comment-15843376 ] David Squier commented on COUCHDB-3013: --- I believe we're also now hitting this issue with CouchDB 2.0. If there is additional information we can provide (i.e., test case), let me know and I'll be happy to help. > Empty selector and empty $and selector not returning same results > - > > Key: COUCHDB-3013 > URL: https://issues.apache.org/jira/browse/COUCHDB-3013 > Project: CouchDB > Issue Type: Bug > Components: Mango >Reporter: Garren Smith > > If I do `selector: {}` I get all the docs returned. > But if I do `selector: {$and: [{}, {}]}` I get 0 docs returned. > I think these queries are the same and should return all docs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] couchdb-documentation pull request #99: Fix documentation contribution guide...
GitHub user satabin opened a pull request: https://github.com/apache/couchdb-documentation/pull/99 Fix documentation contribution guidelines The documentation site now lives in its own git repository. The guidelines are outdated. You can merge this pull request into a Git repository by running: $ git pull https://github.com/satabin/couchdb-documentation update-contribution-guidelines Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-documentation/pull/99.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #99 commit e7725f92d78b3e325be725022945c2dc3958f17e Author: Lucas SatabinDate: 2017-01-27T16:30:11Z Fix documentation contribution guidelines The documentation site now lives in its own git repository. The guidelines are outdated. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---