Skip to content

Add details about rate limits for Operator deployments #2748

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mdlinville wants to merge 4 commits into
base: main
Choose a base branch
from
+35 −2
Open

Add details about rate limits for Operator deployments #2748

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5d2c68d
Add details about rate limits for Operator deployments
mdlinville Jun 9, 2026
d15bcdf
Add GORILLA_LIMITER
mdlinville Jun 9, 2026
31c63f8
Apply suggestion from @mdlinville
mdlinville Jun 9, 2026
17b36de
Merge branch 'main' into DOCS-2575
mdlinville Jun 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion platform/hosting/hosting-options/dedicated-cloud/rate-limits.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,4 +13,4 @@ The following section lists the default rate limits and describes how the W&B SD

<RateLimitsDefaultsAndNotification />

W&B recommends these defaults for typical production workloads. If your workloads consistently exceed these limits, contact [W&B support](mailto:support@wandb.com) or your Account Solutions Engineer (AISE) to request higher limits. Provide details of your experimental setup and usage patterns so that W&B can scope an appropriate adjustment.
W&B recommends these defaults for typical production workloads. See [Set rate limits](/platform/hosting/self-managed/operator#set-rate-limits). If your workloads consistently exceed these limits, contact [W&B support](mailto:support@wandb.com) or your Account Solutions Engineer (AISE) to request higher limits. Provide details of your experimental setup and usage patterns so that W&B can scope an appropriate adjustment.
33 changes: 33 additions & 0 deletions platform/hosting/self-managed/operator.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1759,6 +1759,39 @@ global:
GLOBAL_ENV: "example"
```

### Set rate limits

For Dedicated Cloud and Self-Managed deployments that use the Operator, optionally configure rate limits by setting environment variables in `spec.values.global.extraEnv`. This example shows the default value when the variable is not set.

<Important>You must set `GORILLA_LIMITER` to the address of your Redis server.</Important>
Comment on lines +1764 to +1766

```yaml
spec:
values:
global:
extraEnv:
GORILLA_DEFAULT_RATE_LIMITS_FILESTREAM: "5"
GORILLA_DEFAULT_RATE_LIMITS_FILESTREAM_COUNT: "5"
GORILLA_DEFAULT_RATE_LIMITS_FILESTREAM_PER_RUN_COUNT: "0.8"
GORILLA_DEFAULT_RATE_LIMITS_FILESTREAM_SIZE: "10"
GORILLA_DEFAULT_RATE_LIMITS_GRAPHQL: "50"
GORILLA_DEFAULT_RATE_LIMITS_RUN_UPDATE_COUNT: "10"
GORILLA_DEFAULT_RATE_LIMITS_SDK_GRAPHQL_QUERY_SECONDS: "1"

@jessicaxiang jessicaxiang Jun 15, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would maybe remove the GORILLA_DEFAULT_RATE_LIMITS_SDK_GRAPHQL_QUERY_SECONDS and GORILLA_DEFAULT_RATE_LIMITS_GRAPHQL from the recommendation since we don't set these on dedicated by default.

GORILLA_LIMITER: "redis://[redis-service-address]:6379?ttlInSeconds=900"
```

Refer to the following table for more detail:

| Environment variable | Default | Description |
| --- | --- | --- |
| `GORILLA_DEFAULT_RATE_LIMITS_FILESTREAM` | `5` | Default filestream requests. |
| `GORILLA_DEFAULT_RATE_LIMITS_FILESTREAM_COUNT` | `5` | Filestream requests per second. |
| `GORILLA_DEFAULT_RATE_LIMITS_FILESTREAM_PER_RUN_COUNT` | `0.8` | Filestream requests per per run per second. |
| `GORILLA_DEFAULT_RATE_LIMITS_FILESTREAM_SIZE` | `10` | Filestream ingestion limit in MB per second. |
| `GORILLA_DEFAULT_RATE_LIMITS_GRAPHQL` | `50` | GraphQL requests. |
| `GORILLA_DEFAULT_RATE_LIMITS_RUN_UPDATE_COUNT` | `10` | Run metadata update requests per second. |
| `GORILLA_DEFAULT_RATE_LIMITS_SDK_GRAPHQL_QUERY_SECONDS` | `1` | SDK GraphQL query seconds budget. |
Comment on lines +1785 to +1793

### Custom certificate authority
`customCACerts` is a list and can take many certificates. Certificate authorities specified in `customCACerts` only apply to the W&B Server application.

Expand Down
2 changes: 1 addition & 1 deletion platform/hosting/self-managed/rate-limits.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,4 +11,4 @@ You can configure rate limits on your W&B Self-Managed instance to maintain stab

<RateLimitsDefaultsAndNotification />

W&B recommends these defaults for typical production workloads. If your workloads consistently exceed these limits, you can adjust them (or leave them unset) according to your instance size and shared usage. For configuration details, see [Deploy W&B with Kubernetes Operator](/platform/hosting/self-managed/operator) or contact [W&B support](mailto:support@wandb.com).
W&B recommends these defaults for typical production workloads. If your workloads consistently exceed these limits, you can adjust them (or leave them unset) according to your instance size and shared usage. See [Set rate limits](/platform/hosting/self-managed/operator#set-rate-limits). Contact [W&B support](mailto:support@wandb.com) if you need help sizing these limits for your deployment.
Loading