Low concurrency[🐛 Bug]:

What happened?

V4 grid node utilization is very low compared to V3. In V3 if you had 100 grid nodes ready and registered to the hub and then ran 100 tests in parallel, all 100 grid nodes was immediately put to work but in V4 you can do the same and see only about 12 nodes being utilized. 88 nodes never got tests routed to them. Note: that the queue in this scenario is 0.

Setting a higher “–max-threads” value has no effect and actually we cannot see this parameter being used in the selenium code at all?

How can we reproduce the issue?

We see this consistently with V4.1.2 using java openjdk 11 and latest TestNG. We ruled out TestNG as the issue and verified that when requesting 100 tests in parallel on an empty grid, the queue immediately went to 100.

The grid is started as distributed, hub and nodes on separate AWS VM's.

Relevant log output

Full logs of this event are very large, will try to attach in comments...

Operating System

Ubuntu 20.04

Selenium version

Selenium v4.1.2

What are the browser(s) and version(s) where you see this issue?

Chrome 96

What are the browser driver(s) and version(s) where you see this issue?

96.0.4664.45

Are you using Selenium Grid?

4.1.2

[diemol]

We have fixed this in 4.5.3 but wanted to wait until 4.6 to double check. Closing.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.