Optimizing the performance of a web driver #41
Unanswered
admiral504
asked this question in
Q&A
Replies: 1 comment
-
"Premature optimization is the root of all evil." So, something that works, is better than perfect. Additionally, one of the most critical optimizations is already in place – disabling images, fonts, and CSS: Moreover, many of the optimizations you're suggesting are already incorporated into the Bose Framework. Additionally, if you still wish to add options (though it's unlikely to make any noticeable difference), you can override the create_driver method in the BaseTask class and return a driver with the desired options. Peace :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a question about optimizing the performance of a web driver, and I believe you might be able to help.
I've heard that adding certain options to the code can improve the performance of the web driver. However, I'm not entirely sure how to go about adding these options. Here's the list of options I've come across:
--no-sandbox
--disable-dev-shm-usage
--disable-renderer-backgrounding
--disable-background-timer-throttling
--disable-backgrounding-occluded-windows
--disable-client-side-phishing-detection
--disable-crash-reporter
--disable-oopr-debug-crash-dump
--no-crash-upload
--disable-gpu
--disable-extensions
--disable-low-res-tiling
--log-level=3
--silent
Could you kindly guide me on how to incorporate these options into the code? Your expertise in this matter would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions