Ask the Community
Best practices to set up a Self-Hosted solution
Setting up your Self-Hosted infrastructure correctly ensures optimal test execution at your desired scale. Follow these proven best practices for easy understanding and implementation.
Recommended configuration
Use the following recommendations to achieve the best performance:
| Item | Recommendation | Notes |
|---|---|---|
| Operating System | Linux | Linux generally provides better performance than Windows. |
| Number of Subnets | 3 subnets | Ensures high availability of your infrastructure. |
| Framework and Version | Selenium 4 | Most stable and widely adopted framework. Other frameworks like Playwright or Cypress can also be used based on your preference. |
| Browser Versions | Most recent 3 versions | Recommended for comprehensive, modern testing coverage. |
| Set Up Grid | Use Helm charts | Simplifies configuration with your existing Kubernetes setup. |
| Instance Type | c5a category instances | Optimal for higher parallel execution (100+ parallels). |
CPU allocation per browser
Proper CPU allocation ensures efficient resource utilization and reliable test performance. The following are the CPU allocation recommendations for each browser.
Linux OS recommendations
- Standard websites: Allocate 1.5 CPUs per browser.
- 24x7 testing or intensive websites: Allocate at least 2 CPUs per browser.
- Example: A c5a.2xlarge instance (8 CPUs) supports approximately 5 parallel browser sessions.
Windows OS recommendations
- Standard websites: Allocate 2 CPUs per browser.
- 24x7 testing or intensive websites: Allocate 2.5 CPUs or more per browser.
- Example: A c5a.2xlarge instance typically supports up to 4 parallel browser sessions.
Scaling recommendations
- Configure instances to be always available for performance optimization.
- Use additional instances to scale dynamically as per demand.
- Helm charts can help configure your setup efficiently.
Following these guidelines ensures your infrastructure runs efficiently, scales effectively, and supports your testing needs reliably.
Next steps
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!