0
1.1K
Visualizaçõeshow to open multiple puppeteer instances without effecting it's speed
so what happening to me is when i open 1 puppeteer instance it would go fast a but the more i open the more time it need to load the URL + fill information is that a normal thing ?
const puppeteer = require('puppeteer');
(async () => {
const browser = await puppeteer.launch();
const page = await browser.newPage();
await page.goto('https://example.com');
await page.screenshot({ path: 'example.png' });
await browser.close();
})();
1 Respostas
Responde à pergunta0
Answer
Performance of
- multiple pupeteer instances and
- running on the same machine and
- testing a single application
is highly dependent on the performance of your machine (4 cored , 8 threads , corei7 7700hq)
On my local setup I could not run more than 10 parallel instances and the performance drop was noticeable the more instances I've launched.
My Story
I have faced similar challenge, when I was trying to simulate multiple users using the same application in parallel.
I know: pupeteer (and/or) similar ui-test-automation tools are not good tools for stresstesting your application; or that: there are better tools for that.
Nevertheless, my case was:
- Run "user-like" behavior
- From the other end of the world
- Collect
HARfiles - that represent network timings of the browser interacting with 10-20 different systems - Analyze the behavior
My approach was - maybe this helps you:
- Create a puppeteer test
- Enable headless running
- Make it triggerable via
curl - Dockerize it
- Run the
dockerimage on 10 different machines (5-10dockerized pupeteer tests/machine) - Trigger them all at once via
curl
