Parallelize browser processes rather than pages #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Quramy
changed the title
|
@tsuyoshiwada I also want to parallelize the PREPARE phase. But I do not know when I do it 😅 If I would do this, I open another PR. |
wadackel
reviewed
May 31, 2018
| @@ -1,7 +1,6 @@ | |||
| import * as puppeteer from 'puppeteer'; | |||
| import { EventTypes } from '../constants'; | |||
| import { CLIOptions } from '../../models/options'; | |||
| import { createArray } from '../utils'; | |||
There was a problem hiding this comment.
Since createArray is unnecessary, it may be better to delete it.
|
Hi @Quramy, Thank you for contribute!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've created this for #7 :)
This PR makes parallelization in the
CAPTUREphase more efficient. It because that considering TCP connection restrictions of Chromium, parallelization of browser processes can use CPU more efficiently than parallelization of pages in one browser process.