[GitHub] mikeymckay commented on issue #278: Document best configuration settings for low-spec HW

[GitBox <gi...@apache.org>]

mikeymckay commented on issue #278: Document best configuration settings for low-spec HW
URL: https://github.com/apache/couchdb-documentation/issues/278#issuecomment-447272173
 
 
   In my experience, the biggest problem with couchdb on docker or even my laptop is the q and n values in the clustering section of configuration. @janl pointed me in this direction during an IRC debug session and it has helped tremendously. 
   
   There is some documentation here:
   http://docs.couchdb.org/en/2.2.0/config/cluster.html
   
   But I am still not quite sure how best to setup the q and n values for smaller standalone instances. Here's my simplistic logic (call it cowboy configuration for couchdb), that I would love to have checked/improved:
   
   1) Keep n (the number of replicas) at 1. This is the default, and the defaults seem to be for "beefy servers". We can't go any lower, so 1 it is. Want extra redudancy? - go higher, but I don't know how you would take advantage of this in case a disk died. Seems like it is easier to just replicate data to a backup server.
   
   2) For maximum efficiency let q equal the number of CPU cores on the device. If it's on your laptop and you don't want couchdb to slow down other stuff, make it a few less. On the other hand, if it's a dedicated couchdb instance I expect that threading means you could actually squeeze a bit more efficiency giving yourself one more q than the number of cores, but that is a guess - I'm sticking to q = # of cores.
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services