# 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: circa 13 ore fa
- Author title: Senior DevOps Engineer
- Net upvotes: 1



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

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

## Related discussions
- [Quanto bene si adatta Trello a un team più grande?](https://www.g2.com/it/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: circa 13 anni fa
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/it/discussions/2-can-we-please-add-a-new-section)
  - Posted at: circa 13 anni fa
  - Comments: 0
- [Benefici quantificabili dall'implementazione del tuo CRM](https://www.g2.com/it/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: quasi 13 anni fa
  - Comments: 4