Skip to main content
You can configure rate limits on your W&B Self-Managed instance to maintain stability and prevent one user or workload from negatively impacting others. These limits are optional. If you do not set them, the instance does not enforce the limits described below.

Default limits and notification

The following default limits help maintain platform stability:
LimitDefaultScope
Filestream requests per second500Project
Filestream size120 MB per secondProject
Filestream requests per run per second2Run
Run creation requests per second80Project
When a limit is exceeded, the W&B SDK returns HTTP 429. You may see a message such as the following in your SDK logs:
HTTP 429: rate limit exceeded
These defaults are recommended for typical production workloads. If your workloads consistently exceed these limits, you can configure these limits (or leave them unset) according to your instance size and shared usage. For configuration details, refer to Deploy W&B with Kubernetes Operator or contact W&B support.