feat: run augurs computation in worker thread #750
+87
−23
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.
This is mostly a PoC PR demonstrating how we might do this, in case it comes up in future. I've used workerize-loader to simplify the creation of the worker but we could probably do it by hand to avoid the dependency if we wanted.
Edit: actually I just profiled this and it results in a considerable amount less jank for the 'most relevant' sorting. Here are two profiles where I switch to the Most Relevant sorting, before and after this change; note that in the second one, all of the expensive work is run in the DOM worker, and there's a lot less jank reported.
I think this needs a bunch of double-checking before merging because I may have missed something (e.g. does changing the
publicPath
to be absolute matter? ).