worker performance refactor

Author: jsundai

INFORMATION-ARCHITECTURE.md

@@ -152,8 +152,8 @@ These cross-cutting pages live outside any SDK folder:
 - `plugins-guide.mdx` — How to build plugins; architecture guidance.
 - `integrations.mdx` — Hub page linking to SDK-specific integration guides.
 - `safe-deployments.mdx` — Workflow code deployment strategies, replay testing.
-- `worker-performance.mdx` — Performance tuning, slot suppliers, metrics.
-- `worker-tuning-reference.mdx` — Reference tables for worker config.
+- `worker-performance/` — Performance tuning hub (concepts) plus subpages for metrics, configuration, runtime tuning, Workflow cache, and Task Queue performance.
+- `worker-tuning-reference.mdx` — Reference tables for worker config (sidebar: under Worker performance).
 - `task-queue-priority-fairness.mdx` — Task queue priority and fairness features.
 - `activity-retry-simulator.mdx` — Interactive tool for visualizing retry behavior.
 - `run-a-development-server.mdx` — Installing and running the Temporal CLI dev server.
@@ -169,7 +169,7 @@ These cross-cutting pages live outside any SDK folder:
 - **SDK coverage gaps.** Nexus is missing from PHP and Ruby. Interceptors docs exist only for Python and TypeScript.
   Serverless worker guides exist only for Go, Python, and TypeScript. These gaps may reflect SDK support status, but
   that is not documented anywhere in the section.
-- **Cross-cutting content placement.** Pages like `safe-deployments.mdx`, `worker-performance.mdx`, and
+- **Cross-cutting content placement.** Pages like `safe-deployments.mdx`, `worker-performance/`, and
   `worker-tuning-reference.mdx` straddle Develop and Deploy to production. `safe-deployments` in particular is about
   deployment strategy (versioning vs. patching), which reads more like production deployment guidance.
 - **Setup page naming is inconsistent.** Most SDKs use `set-up-your-local-<language>`, TypeScript uses

docs/best-practices/worker-alerting.mdx

@@ -127,7 +127,7 @@ For triage, see [Worker capacity](/troubleshooting/worker-capacity).
 :::note
 
 `worker_task_slots_available` reports meaningful values only with fixed-size slot suppliers.
-It can't be used with resource-based slot suppliers. See [Slot availability metrics](/develop/worker-performance#slot-availability-metrics).
+It can't be used with resource-based slot suppliers. See [Slot availability metrics](/develop/worker-performance/metrics#slot-availability-metrics).
 If your Workers use resource-based tuning, skip this one and let schedule-to-start latency tell you when capacity is short.
 
 :::

docs/best-practices/worker.mdx

@@ -233,11 +233,11 @@ To get started, focus on these key Worker options:
   how Task slots are assigned to different Task types. Refer to
   [Slot Suppliers](/develop/worker-performance#slot-suppliers) for more details.
 - **Sticky cache size**: Controls the size of the sticky cache for Workflow Executions. Larger caches reduce replay
-  overhead but consume more memory. Refer to [Workflow Cache Tuning](/develop/worker-performance#workflow-cache-tuning)
+  overhead but consume more memory. Refer to [Workflow Cache Tuning](/develop/worker-performance/workflow-cache)
   for more details.
 - **Poller counts**: Controls the number of pollers for Tasks. We recommend you use the Poller Autoscaling feature to
   automatically adjust the number of pollers based on your workload. Refer to
-  [Configuring Poller Options](/develop/worker-performance#configuring-poller-options) for more details.
+  [Configuring Poller Options](/develop/worker-performance/configuration#configuring-poller-options) for more details.
 
 Use the metrics listed in [Interpret metrics as a whole](#interpret-metrics-as-a-whole) to guide your tuning decisions.
 

docs/cloud/metrics/openmetrics/metrics-reference.mdx

@@ -533,7 +533,7 @@ It can overcount because invalid or expired Tasks, like from cancelled, terminat
 
 It can also reset to zero on an idle Task Queue. If no Worker polls, no new Tasks are added, and no other Task Queue calls occur (such as `DescribeTaskQueue` or `UpdateTaskQueueConfig`) for approximately 5 minutes. The Task Queue is unloaded from memory.
 Infrequent metadata updates and database time-to-live settings can also cause this metric to drift at a smaller magnitude.
-See [backlog accuracy limitations](/develop/worker-performance#backlog-accuracy-limitations) for details.
+See [backlog accuracy limitations](/develop/worker-performance/task-queues#backlog-accuracy-limitations) for details.
 :::
 
 | Label | Description |

docs/cloud/worker-health.mdx

@@ -242,9 +242,9 @@ temporal_cloud_v1_approximate_backlog_count{temporal_namespace=~"$namespace", te
 - Verify that your Worker setup is optimized for your instance:
   - Check the system CPU usage against `task_slots` and adjust `maxConcurrentWorkflowTaskExecutionSize` and `maxConcurrentActivityExecutionSize` settings as necessary.
   - Check the system memory usage against `sticky_cache_size` and adjust sticky cache size as necessary.
-  - For a detailed explanation of settings, see the [Worker Performance](/develop/worker-performance#task-queues-processing-tuning) section.
+  - For a detailed explanation of settings, see the [Worker Performance](/develop/worker-performance/task-queues#task-queues-processing-tuning) section.
 - Increase the Worker config for concurrent pollers for Workflow or Activity `task_slots`, if your Worker resources can accommodate the increased load.
-  - Reference [Worker Performance > Poller Count](/develop/worker-performance#poller-count).
+  - Reference [Worker Performance > Poller Count](/develop/worker-performance/task-queues#poller-count).
 - Increase the number of available Workers.
 
 :::warning

docs/develop/go/client/temporal-client.mdx

@@ -682,7 +682,7 @@ if err != nil {
 
 You can configure Task Queues that are host-specific, Worker-specific or Workflow-specific to distribute your
 application load. For more information, refer to
-[Task Queues Processing Tuning](/develop/worker-performance#task-queues-processing-tuning) and
+[Task Queues Processing Tuning](/develop/worker-performance/task-queues#task-queues-processing-tuning) and
 [Worker Versioning](/worker-versioning).
 
 ### Set custom Workflow Id {/* #workflow-id */}