3 ms·
All of the approaches of driving the browser outside of the browser is going to be slow (webdriver, playwright, puppeteer, etc). Karma like approaches are wher
by Robdel12 1y ago
All of the approaches of driving the browser outside of the browser is going to be slow (webdriver, playwright, puppeteer, etc).
Karma like approaches are where I’m at (execute in the browser)
- appcustodian2 1y ago> All of the approaches of driving the browser outside of the browser is going to be slow Why? I would think any cross-process communication through the CDP websocket would have imperceptible overhead compared to what already takes long in the browser: a ton of HTTP I/O What is Karma? What are you executing in the browser?
- nikisweeting 1y agoCDP rountrip time on a local machine is 100µs (0.1ms), it's not slow haha
- johnsmith1840 1y ago"Thousands of cdp calls" from the link. Cdp does add a good chunk of latency. Depends on what your threshold is. An image grab is around 60ms and a snapshot can range from 40ms -> 500ms The latency is pure data movement. It's like the difference of using ram vs ssd vs data from the internet.
- nikisweeting 1y agoyeah but good luck getting rid of that with a browser extension, you're just moving the latency around / moving it to chrome.runtime message passing.