Rewrite of the mutex-based serialization code #129
Merged
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 rewrote the mutex-based serialization code so that a mutex is created for each rendered path, which at least theoretically avoids a bottleneck. It should now also be fully thread-safe.
To avoid opening many handles to the mutexes, I used a simple singleton pattern for the implementation class. It can still be replaced for an instance of BundleBase, in case a test requires it.