Update instance guidance around larger instances and NUMA support

src/current/_includes/common/numa_and_go.md

@@ -2,7 +2,7 @@ In a [NUMA (non-uniform memory access) architecture](https://en.wikipedia.org/wi
 
 CockroachDB is written in Go, which has no process-level support for NUMA scheduling or pinning. Instead, you must manage NUMA at the operating system level. To run multiple CockroachDB clusters on a NUMA architecture:
 
-- Assign no more than 32 cores to the node for each instance. Refer to the documentation for [`numactl --membind`](https://man7.org/linux/man-pages/man8/numactl.8.html).
+- Assign no more than 64 cores to the node for each instance. Refer to the documentation for [`numactl --membind`](https://man7.org/linux/man-pages/man8/numactl.8.html).
 - Ensure that your orchestration framework, process manager, or startup scripts start each CockroachDB in a separate NUMA node.
 - If multiple CockroachDB nodes for the same CockroachDB cluster run on the same physical host, ensure that they are in the same [`--locality`]({% link {{ page.version.version }}/architecture/replication-layer.md %}#intra-locality) to ensure that data is distributed across different physical hosts.
 - Ensure that each CockroachDB node writes to a unique set of storage volumes (block devices).

src/current/_includes/v25.2/prod-deployment/provision-cpu.md

@@ -1 +1 @@
-{% if include.threshold == "absolute_minimum" %}**4 vCPUs**{% elsif include.threshold == "minimum" %}**8 vCPUs**{% elsif include.threshold == "maximum" %}**32 vCPUs**{% endif %}
+{% if include.threshold == "absolute_minimum" %}**4 vCPUs**{% elsif include.threshold == "minimum" %}**8 vCPUs**{% elsif include.threshold == "maximum" %}**64 vCPUs**{% endif %}

src/current/_includes/v25.3/prod-deployment/provision-cpu.md

@@ -1 +1 @@
-{% if include.threshold == "absolute_minimum" %}**4 vCPUs**{% elsif include.threshold == "minimum" %}**8 vCPUs**{% elsif include.threshold == "maximum" %}**32 vCPUs**{% endif %}
+{% if include.threshold == "absolute_minimum" %}**4 vCPUs**{% elsif include.threshold == "minimum" %}**8 vCPUs**{% elsif include.threshold == "maximum" %}**64 vCPUs**{% endif %}

src/current/_includes/v25.4/prod-deployment/provision-cpu.md

@@ -1 +1 @@
-{% if include.threshold == "absolute_minimum" %}**4 vCPUs**{% elsif include.threshold == "minimum" %}**8 vCPUs**{% elsif include.threshold == "maximum" %}**32 vCPUs**{% endif %}
+{% if include.threshold == "absolute_minimum" %}**4 vCPUs**{% elsif include.threshold == "minimum" %}**8 vCPUs**{% elsif include.threshold == "maximum" %}**64 vCPUs**{% endif %}

src/current/_includes/v26.1/prod-deployment/provision-cpu.md

@@ -1 +1 @@
-{% if include.threshold == "absolute_minimum" %}**4 vCPUs**{% elsif include.threshold == "minimum" %}**8 vCPUs**{% elsif include.threshold == "maximum" %}**32 vCPUs**{% endif %}
+{% if include.threshold == "absolute_minimum" %}**4 vCPUs**{% elsif include.threshold == "minimum" %}**8 vCPUs**{% elsif include.threshold == "maximum" %}**64 vCPUs**{% endif %}

src/current/_includes/v26.2/prod-deployment/provision-cpu.md

@@ -1 +1 @@
-{% if include.threshold == "absolute_minimum" %}**4 vCPUs**{% elsif include.threshold == "minimum" %}**8 vCPUs**{% elsif include.threshold == "maximum" %}**32 vCPUs**{% endif %}
+{% if include.threshold == "absolute_minimum" %}**4 vCPUs**{% elsif include.threshold == "minimum" %}**8 vCPUs**{% elsif include.threshold == "maximum" %}**64 vCPUs**{% endif %}

src/current/v25.2/recommended-production-settings.md

@@ -70,6 +70,8 @@ In general, distribute your total vCPUs into the **largest possible nodes and sm
 
 - Cockroach Labs does not extensively test clusters with more than {% include {{ page.version.version }}/prod-deployment/provision-cpu.md threshold='maximum' %} per node. This is the recommended _maximum_ threshold.
 
+- CockroachDB should only run on single-NUMA instances. Running a CockroachDB process across NUMA nodes is not recommended and can heavily impact performance. For more information on how CockroachDB interfaces with NUMA, read the [Linux deployment limitations]({% link {{ page.version.version }}/install-cockroachdb-linux.md %}#numa).
+
 ### Basic hardware recommendations
 
 After you [size your cluster](#sizing), you can determine the amount of RAM, storage capacity, and disk I/O from the number of vCPUs.

src/current/v25.3/recommended-production-settings.md

@@ -64,6 +64,8 @@ In general, distribute your total vCPUs into the **largest possible nodes and sm
 
 - Cockroach Labs does not extensively test clusters with more than {% include {{ page.version.version }}/prod-deployment/provision-cpu.md threshold='maximum' %} per node. This is the recommended _maximum_ threshold.
 
+- CockroachDB should only run on single-NUMA instances. Running a CockroachDB process across NUMA nodes is not recommended and can heavily impact performance. For more information on how CockroachDB interfaces with NUMA, read the [Linux deployment limitations]({% link {{ page.version.version }}/install-cockroachdb-linux.md %}#numa).
+
 ### Basic hardware recommendations
 
 After you [size your cluster](#sizing), you can determine the amount of RAM, storage capacity, and disk I/O from the number of vCPUs.

src/current/v25.4/recommended-production-settings.md

@@ -64,6 +64,8 @@ In general, distribute your total vCPUs into the **largest possible nodes and sm
 
 - Cockroach Labs does not extensively test clusters with more than {% include {{ page.version.version }}/prod-deployment/provision-cpu.md threshold='maximum' %} per node. This is the recommended _maximum_ threshold.
 
+- CockroachDB should only run on single-NUMA instances. Running a CockroachDB process across NUMA nodes is not recommended and can heavily impact performance. For more information on how CockroachDB interfaces with NUMA, read the [Linux deployment limitations]({% link {{ page.version.version }}/install-cockroachdb-linux.md %}#numa).
+
 ### Basic hardware recommendations
 
 After you [size your cluster](#sizing), you can determine the amount of RAM, storage capacity, and disk I/O from the number of vCPUs.

src/current/v26.1/recommended-production-settings.md

@@ -64,6 +64,8 @@ In general, distribute your total vCPUs into the **largest possible nodes and sm
 
 - Cockroach Labs does not extensively test clusters with more than {% include {{ page.version.version }}/prod-deployment/provision-cpu.md threshold='maximum' %} per node. This is the recommended _maximum_ threshold.
 
+- CockroachDB should only run on single-NUMA instances. Running a CockroachDB process across NUMA nodes is not recommended and can heavily impact performance. For more information on how CockroachDB interfaces with NUMA, read the [Linux deployment limitations]({% link {{ page.version.version }}/install-cockroachdb-linux.md %}#numa).
+
 ### Basic hardware recommendations
 
 After you [size your cluster](#sizing), you can determine the amount of RAM, storage capacity, and disk I/O from the number of vCPUs.

src/current/v26.2/recommended-production-settings.md

@@ -64,6 +64,8 @@ In general, distribute your total vCPUs into the **largest possible nodes and sm
 
 - Cockroach Labs does not extensively test clusters with more than {% include {{ page.version.version }}/prod-deployment/provision-cpu.md threshold='maximum' %} per node. This is the recommended _maximum_ threshold.
 
+- CockroachDB should only run on single-NUMA instances. Running a CockroachDB process across NUMA nodes is not recommended and can heavily impact performance. For more information on how CockroachDB interfaces with NUMA, read the [Linux deployment limitations]({% link {{ page.version.version }}/install-cockroachdb-linux.md %}#numa). For more information on how CockroachDB interfaces with NUMA, read the [Linux deployment limitations]({% link {{ page.version.version }}/install-cockroachdb-linux.md %}#numa)
+
 ### Basic hardware recommendations
 
 After you [size your cluster](#sizing), you can determine the amount of RAM, storage capacity, and disk I/O from the number of vCPUs.