Configure SmithDB for scale

SmithDB is optional and available in beta. Use these tiers only after you decide to enable SmithDB. For non-SmithDB LangSmith services, see Configure LangSmith for scale.

Use these tested tiers as starting configurations for SmithDB.

Configure observability before tuning capacity. See Configure SmithDB observability.

Choose and scale a tier

These tiers are starting points, not fixed throughput limits or prescribed configurations. CPU, memory, and ephemeral-storage values are per replica.

Choose the tier whose tested ingestion and query rates most closely match or exceed your expected steady-state load. Apply the per-replica resources and starting replica counts from the selected tier. If the workload later outgrows that starting point, SmithDB compute can be scaled horizontally.

SmithDB query, ingestion, and compaction-worker HPAs are enabled by default. They require Kubernetes Metrics Server or another metrics.k8s.io provider. Verify availability with kubectl get --raw /apis/metrics.k8s.io/v1beta1.

Baseline tiers

Component	Small 10 ingest / 10 query QPS	Medium 100 ingest / 40 query QPS	Large 1000 ingest / 100 query QPS
Ingestion	1 replica 4 CPU 8 Gi memory 100 Gi ephemeral	1 replica 16 CPU 32 Gi memory 100 Gi ephemeral	2 replicas 56 CPU 150 Gi memory 1000 Gi ephemeral
Query	1 replica 4 CPU 8 Gi memory 200 Gi ephemeral	1 replica 28 CPU 48 Gi memory 200 Gi ephemeral	4 replicas 28 CPU 50 Gi memory 1000 Gi ephemeral
Compaction	1 replica 2 CPU 4 Gi memory	1 replica 4 CPU 8 Gi memory	1 replica 8 CPU 16 Gi memory
Compaction worker	1 replica 8 CPU 16 Gi memory 100 Gi ephemeral	3 replicas 16 CPU 32 Gi memory 100 Gi ephemeral	4 replicas 28 CPU 50 Gi memory 300 Gi ephemeral
Cluster manager	1 replica 250m CPU 256 Mi memory	1 replica 250m CPU 256 Mi memory	1 replica 2 CPU 2 Gi memory

Configure resources with Helm

The chart defaults to small. Select small, medium, or large:

smithdb:
  resourceTier: medium

A tier sets per-replica CPU, memory, and ephemeral-storage requests and limits. Replica counts and autoscaling are configured separately. The chart enables autoscaling for query, ingestion, and compaction worker by default. For local-disk components, the ephemeral-storage limit also sizes the generated emptyDir. Explicit component resources or volumes settings take precedence. See SmithDB resource tiers for current values and chart details.

Example explicit resource configuration

To configure resources without smithdb.resourceTier, use the component-level values directly. This medium-tier example is also a copyable reference for overriding individual components:

smithdb:
  query:
    deployment:
      resources:
        requests:
          cpu: "28"
          memory: "48Gi"
          ephemeral-storage: "200Gi"
        limits:
          cpu: "28"
          memory: "48Gi"
          ephemeral-storage: "200Gi"

  ingestion:
    deployment:
      resources:
        requests:
          cpu: "16"
          memory: "32Gi"
          ephemeral-storage: "100Gi"
        limits:
          cpu: "16"
          memory: "32Gi"
          ephemeral-storage: "100Gi"

  compaction:
    deployment:
      resources:
        requests:
          cpu: "4"
          memory: "8Gi"
        limits:
          cpu: "4"
          memory: "8Gi"

  compactionWorker:
    deployment:
      resources:
        requests:
          cpu: "16"
          memory: "32Gi"
          ephemeral-storage: "100Gi"
        limits:
          cpu: "16"
          memory: "32Gi"
          ephemeral-storage: "100Gi"

  clusterManager:
    deployment:
      resources:
        requests:
          cpu: "250m"
          memory: "256Mi"
        limits:
          cpu: "250m"
          memory: "256Mi"

When configuring local-disk components manually, keep limits.ephemeral-storage and any explicit emptyDir.sizeLimit consistent with your Kubernetes policy.

Metastore capacity

The baseline tiers cover SmithDB Kubernetes workloads only. They do not include the PostgreSQL metastore. Use these provisional starting points for a dedicated metastore:

Tier	vCPU	Memory
Small	2	16 GiB
Medium	4	32 GiB
Large	8	64 GiB

Choose the nearest supported PostgreSQL instance shape from your provider and monitor database resource use and transaction latency during rollout.

Get started by cloud provider

Deploy with Terraform

Setup guides

Configuration

Connect external services

SmithDB (optional)

Platform auth & access control

Self-hosted observability

Hybrid

Scripts

Reference

Choose and scale a tier

Baseline tiers

Configure resources with Helm

Metastore capacity

See also

​Choose and scale a tier

​Baseline tiers

​Configure resources with Helm

​Metastore capacity

​See also

Choose and scale a tier

Baseline tiers

Configure resources with Helm

Metastore capacity

See also