forum.e-valid.com

If you're limited on the number of BUs due to machine constraints are you also limited by the number of windows (browser launched subwindows)? Might this gain you some scaling leverage?

fortiis wrote:If you're limited on the number of BUs due to machine constraints are you also limited by the number of windows (browser launched subwindows)? Might this gain you some scaling leverage?

That is a very good question.

To rephrase it a bit, what you are asking is, what is the tradeoff between running multiple sessions based in one eValid browser, and running multiple users on the machine, both methods intended to maximize the number of BUs you have in parallel.

It won't be news to hear, "It depends..."!!!

The variable is the script itself. Think of two extremes: a high-duty-cycle
script and a low-duty-cycle script. For the high-duty-cycle one, you will not gain much using multiple BUs controlled in one eValid instance, which is better for the low-duty-cycle case.

Every situation is different, and the only really general rule we know about this is that you have a good change to amplify BU counts if you can put multiple low-duty-cycle scripts under a single eValid BU. Then you have the option to run more BUs for more equivalent load.

eValid Support