Experiments with performance of setting wellbores in module #35
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.
Some experiments with performance. For Troll it takes 2-3 seconds before all wellbores are rendered using batching. Running a single batch runs in ~1 sec, adding all children in one go seems to shave off ~200ms. Tried using Pixi.BitmapText instead of Pixi.Text as Pixi.Text is drawn to a texture using the canvas API into a texture per label, in theory BitmapText should be more performant as it uses a single texture. Switching to Troll from other field sometimes takes as little as 600ms for adding wellbores using this, however this is not stable as it crashes after changing pages. Not sure if a 600ms freeze would be acceptable (much faster for all other fields. f.ex. snorre takes <100ms), IMHO showing the wellbores faster provides a better user experience than having an animation which renders the same wellbores in1-2 seconds although the animation looks nice.