Enhancing UC Opening Speed

[lucasmarquex]

Before asking my question, I'd like to congratulate you on your work with Undetected Chromedriver (UC), Michael. It has proven to be much more stealthy than the UC from Ultrafunk Amsterdam.

My question is: Chrome, when used with SeleniumBase, takes about 3 seconds to open, whereas Undetected Chromedriver opens in 0.5 seconds. Is there any way to speed up the opening process? I can only open one window at a time using UC due to conflicts, so I'm using threading.Lock, and this significantly impacts the use of multiple windows.

Is there any way to disable all seleniumbase features except UC and make it open faster? Or determine the port so there is no conflict and you can open several windows simultaneously?

[mdmintz]

Hello! You'll find your answer in the driver-specific methods added during UC Mode:

driver.uc_open(url)
driver.uc_open_with_tab(url)
driver.uc_open_with_reconnect(url, reconnect_time=None)
driver.reconnect(timeout)
driver.uc_click(selector)
driver.uc_switch_to_frame(frame)

Use driver.uc_open_with_reconnect(url, reconnect_time) with a short reconnect_time, eg. 0.5 seconds. It's set to around 3 seconds so that there's enough time to get past a Cloudflare verification check before Selenium reconnects to the browser, which makes it detectable.

If you want to open a webpage with no delay at all while using UC Mode, then use driver.default_get(url). That will make you detectable, but it might be that you don't always need to avoid detection when opening web pages.

For multithreading, use the pytest format, which has a special option for that. More info: #2006 (comment)

[lucasmarquex]

I am referring that there is this delay in opening the browser (chrome.exe process), with seleniumbase, opening becomes slow

[mdmintz]

If it's the initial browser open after downloading chromedriver (which gets renamed as uc_driver in UC Mode) then there is an expected pause for uc_driver getting modified so that the driver no longer makes Selenium detectable in the browser.

[lucasmarquex]

Even without seleniumbase's UC mode and with the chrome driver already installed, it usually takes 4x longer than undetected_chromedriver, some initial check is generating a lot of extra time to open the browser process with chromedriver

[mdmintz]

Could you identify the bottleneck for me? I haven't seen it, but maybe it's specific to your OS. Put a breakpoint() in your code and see if you can trace where the issue is originating. If there's a real issue, I may be able to fix it.

[lucasmarquex]

Test:

Result:

[mdmintz]

It should be Driver(uc=True) ... not Driver(uc=uc) (where your uc is where you imported undetcted_chromedriver into.

[lucasmarquex]

Corrected, the result was the same

[lucasmarquex]

Does the interference problem have to do with using port 9222? Because it seems to be a difference between UC mode and undetected_chromedriver. And what is the difference between being undetectable between the two? The difference is that Seleniumbase's UC mode handles the created profile?

[mdmintz]

It'll use port 9222 if available. Otherwise it'll find another free port. The modes work very similarly.

Will need more info as to why you're seeing the slowdown. Will likely need breakpoint() and a specific line where the slowdown occurred.

[lucasmarquex]

What is the difference between the two libs? because seleniumbase ucmode has interference with multiple windows and undetected_chromedriver does not

[mdmintz]

SeleniumBase has a larger API, more features, more customization options, etc, but the general algorithm for avoiding detection is similar. SeleniumBase tweaks the algorithm a bit so that it can bypass detection on more websites.