PhantomJS: Archiving the project, suspending development

Re:PhantomJS: Archiving the project, suspending development by Analemma_ on Saturday March 03, 2018 @10:43PM (#16513144)

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?

[ Parent | on HN ]

Re:PhantomJS: Archiving the project, suspending development by vaviloff on Saturday March 03, 2018 @11:20PM (#16513245)

Also PhantomJS was a single statically linked binary with no dependencies that you could literally drop into a server and run scripts at once.

[ Parent | on HN ]

Re:PhantomJS: Archiving the project, suspending development by oelmekki on Sunday March 04, 2018 @03:42AM (#16513817)

For 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

godet is the lib I use for chrome piloting, replace with your favorite one.

[ Parent | on HN ]

Re:PhantomJS: Archiving the project, suspending development by cowkingdeluxe on Monday March 05, 2018 @09:07AM (#16521094)

Running 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/ind... .

[ Parent | on HN ]

Re:PhantomJS: Archiving the project, suspending development by pbiggar on Sunday March 04, 2018 @12:09AM (#16513357)

I have the same problem, so it's not just you.

[ Parent | on HN ]

Re:PhantomJS: Archiving the project, suspending development by gowan on Monday March 05, 2018 @11:49AM (#16522323)

this is one of the reasons i created chromedriver-proxy[0]

[0] https://github.com/ZipRecruiter/chromedriver-proxy

[ Parent | on HN ]