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
{{ message }}
This repository has been archived by the owner on Dec 11, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
ckmoga
changed the title
Kite launch more browsers than specified
Kite launches more browsers than specified
Jul 25, 2021
Hello,
Changing DEFAULT_MAXINSTANCES shouldn't impact anything, as you are already running your grid through the command 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.
It is only used to automate the launch of the grid, which is not available unless you implemented it on your side.
I tried to reproduce your issue but 25 browsers are opening, as expected.
Can you confirm from the grid console available from http://localhost:4444/grid/console that it is indeed 25 sessions?
@ckmoga Hey, I am not sure if this is the problem but I see in Client.java there is a variable called count and its default value is set to 5. That might be causing some kind of unintended multiplication.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: