Overview
Run Parasail in production with rate-limit handling, quota planning, dedicated scaling, batch operations, and safe retries.
Last updated
Run Parasail in production with rate-limit handling, quota planning, dedicated scaling, batch operations, and safe retries.
This hub links to the operational topics you need when running Parasail in production. Each section points to the page that owns the details.
Rate limits and 429 responses
RPM limits per product tier, throttling behavior, and rate-limit increases
Quota management
GPU quota across Batch and Dedicated, quota errors, and increase requests
Autoscaling and replicas
Max concurrent requests, target concurrency, smoothing, and replica ranges
Batch job lifecycle
Submission, priority, status polling, cancellation, and terminal states
Batch troubleshooting
Validation, file-size limits, stuck jobs, partial failures, and quota errors
Retries and idempotency
429 handling, exponential backoff, timeouts, and safe retry limits
Use the controls documented elsewhere in the docs to keep workloads predictable:
Dedicated status page: Each Dedicated Instance has a status page for viewing deployment status and controlling the endpoint. See Dedicated Instances.
Pause to stop billing: Dedicated Instances bill while active. Pause an endpoint when it isn't needed, and use autoscaling settings to control replica counts. See Auto-Scaling.
GPU quota: The default GPU quota limits the amount of Batch and Dedicated capacity an organization can consume. See Limits and quotas.
Batch status: Track batch jobs in the Batch UI or poll status through the API. See Batch Troubleshooting.
Limits and quotas—request rate limits, GPU quota, and quota increase guidance.
Retries and Idempotency—handle transient errors safely.
Auto-Scaling—size replicas for production traffic.
Last updated