Skip to content

Comment on Running Headless Selenium with Chromeparent

Comments

Why is the overhead so great?

Because it has to load a virtual frame buffer (Xvfb), the chrome browser, a Selenium server, and then your testing framework. All that adds up to crap performance. There's a lot of pieces that could be simplified with a smaller set of requirements. But like @diminoten said: it's worth it if you have no other choice.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.