4 ms·
There is one thing about this that saddens me: PhantomJS still starts up much faster than headless Firefox or Chrome, at least for me, which makes some of our i
by Analemma_ 9y ago
There is one thing about this that saddens me: PhantomJS still starts up much faster than headless Firefox or Chrome, at least for me, which makes some of our integration tests take a long longer than they should.
Has anyone here figured out any tricks to get headless Chrome booted fast?
- vaviloff 9y agoAlso PhantomJS was a single statically linked binary with no dependencies that you could literally drop into a server and run scripts at once.
- oelmekki 9y agoFor those who may struggle with using chrome headless on server, here is a dockerfile example to get your started : https://github.com/oelmekki/chromessr/blob/master/Dockerfile https://github.com/oelmekki/chromessr/blob/master/Dockerfile godet is the lib I use for chrome piloting, replace with your favorite one.
- pbiggar 9y agoI have the same problem, so it's not just you.
- cowkingdeluxe 9y agoRunning it as a pooled web server via generic-pool makes it run a bit more efficiently. Using the pooling method, it can do 512x512 images every 400 ms, add in Optimize, WebP & S3 for a total 1000 ms. I based the pool off of https://github.com/latesh/puppeteer-pool/blob/master/src/index.js https://github.com/latesh/puppeteer-pool/blob/master/src/ind... .
- gowan 9y agothis is one of the reasons i created chromedriver-proxy[0] [0] https://github.com/ZipRecruiter/chromedriver-proxy https://github.com/ZipRecruiter/chromedriver-proxy