Before deploying the Genesys Co-browse solution to your production site, you should estimate the solution size needed to handle your expected user load. Genesys recommends using the Co-browse Sizing Calculator, an Excel workbook that helps you calculate the number of Co-browse Server nodes required for your production deployment.
For Co-browse load capacity planning, use the following input parameters in the Co-browse Sizing Calculator:
- Expected maximum parallel Co-browse sessions
- Website complexity. In the Sizing Calculator, you can select from two boundary options, average (genesys.com) and high (amazon.com). Choose high if your website is highly dynamic, and interactive. For example, websites including a large single-page application, a lot of multimedia content, and/or dynamic page options should select high website complexity.
- WebSocket connection availability
- CPU cores per node, 8 or 4
To achieve the best performance, we highly recommend WebSocket support. Genesys Co-browse enables WebSockets by default. WebSocket-based Co-browse sessions appear smoother to users and consume significantly less traffic by avoiding HTTP overhead. The Co-browse server also consumes less hardware resources when using WebSockets and you may require fewer nodes for your Co-browse cluster.
If you use WebSockets, make sure your load balancers, proxies, and firewalls allow WebSocket connections through. Co-browse uses either WebSockets (ws://) or secure WebSockets (wss://) depending on your website instrumentation.
Since Co-browse server nodes do not share many resources besides the Cassandra cluster, you have nearly linear scalability from your Co-browse cluster. Each node adds the same amount of capacity to the cluster.
For high-availability purposes, we recommend at least one additional server to handle the load in case of server failure. The Co-browse Sizing Calculator includes this recommendation. The Sizing Calculator recommends no fewer than two nodes, even if the single server capacity can handle estimated server load.
Cassandra Cluster Deployment
Most Cassandra clusters should sufficiently support a Co-browse cluster because the Co-browse solution does not produce large amounts of data to store. Confirm that your Cassandra cluster provides enough availability and capacity.