Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Sync Gateway tutorial sample sets GOMAXPROCS to 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.

 

Release Notes Description

None

Activity

Simon Murray April 22, 2021 at 8:06 AM

What's there is right, for most platforms it will set the pod resources to something like 100m cores.  If we wanted to document higher numbers of go routines, then we'd also need to delve into the world of resource scheduling.  Simple enough for inclusion in 2.2.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Story Points

Components

Sprint

Fix versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created April 21, 2021 at 6:42 PM
Updated April 29, 2021 at 1:59 AM
Resolved April 28, 2021 at 12:30 PM
Instabug