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 affecting others. These limits are optional. If you don’t set them, the instance doesn’t enforce any limits.

​
Default limits and notification

The following default limits help maintain platform stability:
LimitDefaultScope
Filestream requests per second500Project
Filestream ingestion per second120 MBProject
Filestream requests per second2Run
Run creation requests per second80Project
When a limit is exceeded, the W&B SDK returns HTTP response 429, and the message HTTP 429: rate limit exceeded appears in the SDK logs. How the SDK responds depends on which limit was exceeded:
  • Filestream rate limits don’t cause logging to crash or fail. When the SDK receives a 429 response on a filestream request, it backs off and retries the rate-limited request as-is, while subsequent updates accumulate.
  • Run creation rate limits block further training. 
HTTP 429: rate limit exceeded
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 or contact W&B support.