Add performance note for parsing source geometry #79252
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds performance note for parsing source geometry.
smix8
added
enhancement
documentation
topic:navigation
cherrypick:4.1
clayjohn
approved these changes
Jul 9, 2023
|
Thanks! |
YuriSizov
removed
the
cherrypick:4.1
|
Cherry-picked for 4.1.1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds performance note for parsing source geometry.
Related to #68642.
Performance problems from reading
Meshresources in the navigation mesh baking process are common. Reading back the mesh data from theRenderingServerandGPUis slooooow.Users do not necessarily know that their performance problems, when parsing source geometry for the navigation mesh baking on the main thread, are often related to the used resource type and not the parsing process in general.