Improved Profile()
inference timing
#9024
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.
🛠️ PR Summary
Made with ❤️ by Ultralytics Actions
🌟 Summary
Implemented a more accurate and granular profiling system in YOLOv5.
📊 Key Changes
Profile
class instances for timing blocks.with Profile():
) for precise measurements.Profile
class to handle timing with automatic CUDA synchronization if necessary.time_sync()
function in favor of Profile class.🎯 Purpose & Impact
Profile
, there's fine-grained timing which should lead to better optimization decisions.Profile
makes future updates to profiling easier and less error-prone.