Show HN: Which is faster? Puppeteer, Playwright or Selenium

Re:Show HN: Which is faster? Puppeteer, Playwright or Selenium by eneuman on Saturday September 09, 2023 @12:36PM (#37447249)

- Language Choice (JS vs Python): Puppeteer in JS and Playwright in Python showed near-identical performance on an AWS c5.large instance. This negated the need to test Puppeteer and Playwright in the same language for this comparison.

- Playwright Scrolling: To emulate a user experience, all three tools employed infinite scrolling, which was necessary since Wallapop doesn't have pagination, you have to scroll to get results.

- Explicit Timeouts: Used for greater stability, especially when contending with network inconsistencies. Initially, I used API response events for triggering scrolls, but this approach was less reliable.

- Evaluate vs. Locators & Click: My initial tests indicated evaluate was marginally faster than locators and click.

I appreciate the scrutiny and I might include a JS vs Python comparison in a future test.

[ Parent | on HN ]

Re:Show HN: Which is faster? Puppeteer, Playwright or Selenium by CharlieDigital on Saturday September 09, 2023 @03:08PM (#37449178)

I think the approach misses the point. Playwright's auto-wait with `locators` is what makes it worth adopting because it means you don't need to use fixed waits. Auto-waits save much of the idle time waiting.

[ Parent | on HN ]