(chromeredir) added some limits to number of open chrome pages #12
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.
chrome really does not like having > 1000 pages open, tried only doing 20 for now
I got a little excited yesterday and did not think to test at scale (as your tools are often run). I tried running what I wrote yesterday with 1000 hosts and it really did not like it, so I have made some changes. Sorry for the double PR, I will try to be a little more thoughtful going forward.
Here are some very rough metrics from my testing today (only ran each test once or twice and on my hardware so ymmv)
It is a little hard to parse, the tl;dr is that it appears that performance is best with 20-50 workers, so I have set the default to 20 as that is in line with your other tools (from what I can tell)
Regardless I do believe this is an improvement from both yesterday and the original, if there is interest I can keep working on / help work on this more as I don't think it is perfect yet (but what ever really is?).
Thanks for the quick response yesterday, it's great to see how involved you are with your projects