puppeteer-cluster | 易学教程

Is Puppeteer-Cluster Stealthy enough to pass bot tests?

阅读更多关于 Is Puppeteer-Cluster Stealthy enough to pass bot tests?

问题 I wanted to know if anyone using Puppeteer-Cluster could elaborate on how the Cluster.Launch({settings}) protects against sharing of cookies and web data between pages in different context. Do the browser contexts here, actually block cookies and user-data is not shared or tracked? Browserless' now infamous page seems to think no, here and that .launch({}) should be called on the task, not ahead of the queue. So my question is, how do we know if puppeteer-cluster is sharing cookies / data

puppeteer-cluster: queue instead of execute

阅读更多关于 puppeteer-cluster: queue instead of execute

问题 I'm experimenting with Puppeteer Cluster and I just don't understand how to use queuing properly. Can it only be used for calls where you don't wait for a response? I'm using Artillery to fire a bunch of requests simultaneously, but they all fail while only some fail when I have the command execute directly. I've taken the code straight from the examples and replaced execute with queue which I expected to work, except the code doesn't wait for the result. Is there a way to achieve this anyway

puppeteer-cluster: queue instead of execute

阅读更多关于 puppeteer-cluster: queue instead of execute

I'm experimenting with Puppeteer Cluster and I just don't understand how to use queuing properly. Can it only be used for calls where you don't wait for a response? I'm using Artillery to fire a bunch of requests simultaneously, but they all fail while only some fail when I have the command execute directly. I've taken the code straight from the examples and replaced execute with queue which I expected to work, except the code doesn't wait for the result. Is there a way to achieve this anyway? So this works: const screen = await cluster.execute(req.query.url); But this breaks: const screen =

Unable to Run Multiple Node Child Processes without Choking on DigitalOcean

阅读更多关于 Unable to Run Multiple Node Child Processes without Choking on DigitalOcean

问题 I've been struggling to run multiple instances of Puppeteer on DigitalOcean for quite some time with little luck. I'm able to run ~5 concurrently using tools like puppeteer-cluster, but for some reason the whole thing just chokes with little helpful messaging. So, I switched to spawning ~5 child processes without any additional library -- just Puppeteer itself. Same issue. Chokes with no helpful errors. I'm able to run all of these jobs just fine locally, but after I deploy, I hit these walls