Skip to content

Conversation

@krichprollsch
Copy link
Member

No description provided.

@krichprollsch
Copy link
Member Author

I used the benchmark on my own computer to compare a release build between main and this PR:
main

$ npm run bench-puppeteer-cdp

> demo@1.0.0 bench-puppeteer-cdp
> node puppeteer/cdp.js

................................................................................
....................
total runs 100
total duration (ms) 25686
avg run duration (ms) 253
min run duration (ms) 187
max run duration (ms) 316

this PR

$ npm run bench-puppeteer-cdp

> demo@1.0.0 bench-puppeteer-cdp
> node puppeteer/cdp.js

................................................................................
....................
total runs 100
total duration (ms) 29046
avg run duration (ms) 287
min run duration (ms) 187
max run duration (ms) 332

@krichprollsch
Copy link
Member Author

But we still use 3.2% of my CPU for doing nothing...
image

@krichprollsch krichprollsch marked this pull request as draft October 29, 2024 09:11
@krichprollsch krichprollsch added the CDP Chrome Debug Protocol label Oct 29, 2024
@francisbouvier
Copy link
Member

Closed in favor of #302

@krichprollsch krichprollsch deleted the sleep-loop branch April 9, 2025 06:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CDP Chrome Debug Protocol

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants