|  PixLab  |  Developer Community, Solved Support Threads & API Knowledge Base


PixLab Background Removal API: Pro Plan Quota vs. 50K Images & 100 Concurrent Users/Sec

Asked
Modified
Viewed 23119 times
18

Hi everyone,

We need to process 50,000 images using the PixLab background removal API. Anticipated traffic is around 100 concurrent user requests per second.

We are on the Pro plan, which offers 150K Media Analysis API calls per month. The monthly volume is fine (50k < 150k limit), but I have a specific question regarding rate limits.

Does the Pro plan include sufficient QPS (queries per second) to handle 100 users/sec, or will we be throttled? Since the monthly quota and the concurrent rate limit are separate metrics, I want to confirm if the Pro tier allows a 100 QPS burst, or if we need to string requests in a queue. If not, should we upgrade to Enterprise or request a custom QPS modification?

Issue Category: Limit or Quota Increase

Looking for clarity on how the monthly API calls interact with the per-second limit. Any advice or direct staff confirmation on the exact QPS allowed on the Pro plan would be appreciated.


Accepted Solution

35

Hello,

Thank you for reaching out to us regarding your background removal requirements.

To clarify, there are two separate metrics to consider: monthly API call quota and concurrent request throughput (requests per second).

1. Monthly Quota (50k images):
The Pro plan provides 150,000 Media Analysis API calls per month. Your expected volume of 50,000 images falls well within this limit, so the monthly quota is not a concern. Refer to the Pricing Page for additional information.

2. Throughput (100 users/sec):
This is the critical factor. The Pro plan includes standard rate limits, typically ranging from 5 to 20 requests per second, depending on the specific API. A sustained peak of 100 concurrent requests per second exceeds the Pro plan's standard rate limits. This would result in HTTP 429 rate-limit errors, queuing delays, or failed requests, meaning your workload would **not** run "perfectly" under peak load.

Recommendation:
To reliably handle 100 requests per second, you would need our Enterprise plan, which offers:
- Custom or unlimited rate limits (meeting your 100 RPS requirement).
- Dedicated infrastructure to handle high concurrency.
- A Service Level Agreement (SLA) for uptime and performance.

In summary, the Pro plan covers your monthly volume but not your concurrency needs. We recommend discussing your expected peak load further or requesting a custom Enterprise quote.