-
-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve performance for concurrent conversions by re-using browser context #141
Improve performance for concurrent conversions by re-using browser context #141
Conversation
5ca5133
to
0094ca7
Compare
Nice, looks cleaner. Didn't like my approach with the passing either 👍 |
Heyo, just tested this Branch.
Gets called many times in concurrent mode. I see no other posibility than creating a browser instance at a higher level, await this, and then start the conversion processes. As I mentioned, maybe a class based approach could help here. |
Possible Solution: |
…ateOutput` concurrently
Ah yup makes sense and that actually explains the problem I was seeing with it hanging when running concurrent tasks! Because it created a bunch of browser instances simultaneously but only closed the last one. It was too late yesterday 😅 (I started falling asleep while working on this) I just fixed it... didn't merge your PR though because it was missing the part where we don't need to call |
All tests passing but @chamabreu if you could test this branch one more time with your 90 files I'd be even more confident to merge this 🤓 |
Replaces #139.
Closes #138.