Re:Show HN: Chrome Remote Debugging Protocol interface
by wslh on Monday August 29, 2016 @08:34AM
(#12381408)
A few years ago I used the Chrome remote interface and was very slow comparing to embedding a web control object for automation. How does it work now?
[ Parent
| on HN ]
Re:Show HN: Chrome Remote Debugging Protocol interface
by cyrusand on Monday August 29, 2016 @11:43AM
(#12382634)
Actually I didn't notice such thing when I used it extensively around 2013 for instrumenting some page loads. Which part was slow in your experience?
Re:Show HN: Chrome Remote Debugging Protocol interface
by wslh on Monday August 29, 2016 @11:54AM
(#12382738)
If I remember well was slower than using HTMLUnit (http://htmlunit.sourceforge.net/) that is written in Java, and it was much slower than writing a browser extension to achieve the same task.
Re:Show HN: Chrome Remote Debugging Protocol interface
by cyrusand on Monday August 29, 2016 @03:46PM
(#12384692)
I see, well I've never performed any benchmark but it's quite possible that an ad hoc headless browser performs better for what concerns repeated tests. On the other hand, in this case you're instrumenting a real (really employed by the final user) browser. Possibly things will improve with this new headless mode for Chrome.
In any case this JavaScript module should not introduce any performance degradation, but if it does and you happen to give it a try in the future, feel free to open an issue.