Slow "Browser" instance creation w/ Headless Chrome GAE Standard Node.js

[kylewill]

I was able to successfully set up the example Headless Chrome demo on GAE Standard with the new runtime.

However, I'm seeing 10-40 second latency for screenshots (no changes to the code). In stackdriver, 6-9 seconds of the latency is due to the puppeteer.launch call. This is incredibly long.

Understand the new GAE Standard Node.js runtime is in Beta, logging to keep track of any updates as several projects will be enabled by usability here.

[kylewill]

Just deployed the same app to GAE Flex, the puppeteer.launch step is 0ms in stackdriver vs 6000-9000ms on GAE Standard

[steren]

Thanks for the feedback.
We are aware of a latency issue with Headless Chrome on App Engine standard and are working on improving the underlying infrastructure.

[fhinkel]

ping @steren is this still an issue?

[steren]

This is being discussed in puppeteer/puppeteer#3120.

Because this is not the sample's fault, I suggest to close this issue in favor of puppeteer/puppeteer#3120

[kylewill]

@steren will close and watch puppeteer/puppeteer#3120