This repository was archived by the owner on Dec 11, 2023. It is now read-only.

Description
I am running headless chrome with the following setups:
"tupleSize": 25
java -Dwebdriver.chrome.driver=./chromedriver.exe -jar ../selenium.jar -role node -maxSession 25 -port 6001 -host localhost -hub http://localhost:4444/grid/register -browser browserName=chrome,version=91,platform=WINDOWS,maxInstances=25 --debug
What I noticed is when launched, Kite creates
125 Chrome sessions
When I change DEFAULT_MAXINSTANCES = 6 in org.webrtc.kite.config.client.Capability, the number of instances sessions jumps to 150
Changing DEFAULT_MAXINSTANCES to a lower value has no impact.
What I am expecting 25 sessions, one for each student, nothing more. What am I missing? This is a massive resource drain and causes 100% spike when more users are added.