Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-2140

Sync Gateway tutorial sample sets GOMAXPROCS to 1

    XMLWordPrintable

Details

    • Page
    • Resolution: Fixed
    • Major
    • 2.2.0
    • None
    • documentation
    • 18: PE/Tasks/Docs
    • 1

    Description

      The Sync Gateway tutorial in the AO docs includes a sample config that sets GOMAXPROCS to 1.

      https://docs.couchbase.com/operator/current/tutorial-sync-gateway.html#deploying-sync-gateway

      It generally wouldn't be recommended to run Sync Gateway on a single core when more cores are available.  SG non-container deployments treat 8 cores as the minimum recommended value.

      I don't know the details of the challenges in setting GOMAXPROCS in k8s environments, other than the fact that there may be challenges compared to a non-container deployment where go applications will default GOMAXPROCS to the number of available cores.

      It's also not recommended to set GOMAXPROCS to something more than the number of available cores, so it isn't the case that this value should just be bumped to 8 or 16.

      I'd like some input from k8s experts on what the value in the sample config should be, but also recommend we add a note to this setting describing how customers should tune to the number of available cores.

       

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            simon.murray Simon Murray
            adamf Adam Fraser
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty