Skip to content

Default Infrastructure Sizing is to small to support more then just functionality testing

The default sizing of the infrastructure and service replicas needs to be increased slightly to support a more common usage pattern for a default OSDU usage.

Minimum Supported Storage Rate

  • Concurrency: 10 threads.
  • Batch Size: 150.
  • Records: 50,000.
  • Time: ~ 8:00 minutes.

Default Configuration *New

AKS Cluster

  • Node Count: 5
  • Server Size: Standard_E4s_v3. (4x32)
  • Subnet Size: /23
  • AKS Version: 1.18.8

Cosmos DB

  • Throughput Auto Scale Shared RU’s: 12000

OSDU Service Replicas

Partition:

  • Replicas: 2
  • Requests CPU: 100m
  • Limits CPU: 300m

Entitlements:

  • Replicas: 2
  • Requests CPU: 100m
  • Limits CPU: 300m

Legal:

  • Replicas: 2
  • Requests CPU: 100m
  • Limits CPU: 300m

Storage:

  • Replicas: 10
  • Requests CPU: 100m
  • Limits CPU: 800m

Indexer-Queue:

  • pollingInterval: 30
  • cooldownPeriod: 60
  • minReplicaCount: 1
  • maxReplicaCount: 10

Indexer:

  • Requests CPU: 100m
  • Limits CPU: 500m
  • HPA:
    • minReplicas: 2
    • maxReplicas: 5
  • cpu:averageUtilization: 75

Ingress Annotations

  • appgw.ingress.kubernetes.io/request-timeout: "300"
  • appgw.ingress.kubernetes.io/connection-draining: "true"
  • appgw.ingress.kubernetes.io/connection-draining-timeout: "30"