# How do you handle Proxy-Seller limits when scaling location-based Selenium testing?

Proxy-Seller has been reliable for location accuracy across targeted markets, and it has been easy to add new locations as our application grew. Connection speeds have stayed consistent enough to keep page load times realistic, which made our automated testing more predictable. The main challenge was missing documentation on technical limits like max concurrent connections or request rate limits, which led to trial and error during the first integration. How have you found or validated these limits, and what helped you scale requests across locations smoothly?

##### Post Metadata
- Posted at: 16 days ago
- Author title: Senior DevOps Engineer
- Net upvotes: 1



## Related Product
[Proxy-Seller](https://www.g2.com/products/proxy-seller/reviews)

## Related Category
[Proxy Networks](https://www.g2.com/categories/proxy-networks)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: about 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: about 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: about 13 years ago
  - Comments: 4