Rem runner loops; use OpenCV #2
Open
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.
Remove TPU Runner loop threads. Instead just have TPUs in queues when ready for usage. Allows for better optimizations and fewer thread context switches. Runs faster with smaller models, up to 700 FPS with several TPUs. Also enables more types of optimizations. Now we track which TPU runs a particular segment faster and swap segments between TPUs to reduce bottlenecks.
Use OpenCV when installed. WILL NEED ADDITIONAL WORK TO VERIFY GOOD FALLBACK FUNCTIONALITY TO PIL. OpenCV is a large package, but contains good AVX optimizations for much faster image resizing.
Latest version of segmented files, now including YOLOv9. Includes new testing of multiple input tensor sizes to get around TPU internal memory. This will need work to ensure the expected files are in the expected places with the expected names.
New versions of archived TPU files available here:
https://drive.google.com/file/d/136o-0C8Z8G5ZUqq1Z_9wQV2KsjVSOZk6/view?usp=drive_link