You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, love the setup you guys have provided. Running 3 machines behind the load balancer each with 2 Splash instances each. Quick question:
Do regular HTTP rules apply here in regards to how many active connections you can have? Say there are Splash requests going out to pull from site-b.com. And let's say I had multiple splash instances (on the same machine, so same IP) all requesting a page from site-b.com simultaneously. Would one or more of these connections have to wait until the active connection finishes?
I ask because I'd like to increase the number of Splash instances on each machine, currently they're only using about ~40% CPU. But just want to make sure I won't be negatively impacting the service, as many of the requests pushed through Splash will be requesting the same domain.
The text was updated successfully, but these errors were encountered:
Hey, love the setup you guys have provided. Running 3 machines behind the load balancer each with 2 Splash instances each. Quick question:
Do regular HTTP rules apply here in regards to how many active connections you can have? Say there are Splash requests going out to pull from site-b.com. And let's say I had multiple splash instances (on the same machine, so same IP) all requesting a page from site-b.com simultaneously. Would one or more of these connections have to wait until the active connection finishes?
I ask because I'd like to increase the number of Splash instances on each machine, currently they're only using about ~40% CPU. But just want to make sure I won't be negatively impacting the service, as many of the requests pushed through Splash will be requesting the same domain.
The text was updated successfully, but these errors were encountered: