Replies: 1 comment
-
| 
         PROBLEM SOLVED! After investigating and optimizing this issue, I've developed a solution that provides 5x performance improvement: Before vs After Results: 
 Root Cause Analysis: Old methodfor slice in slices: Pull Request: Implementation Details: 
 The issue was that SAHI was underutilizing GPU resources by: 
 The solution batches all slices into a single tensor, performs one GPU inference call, then maps results back to original coordinates. Performance Metrics: 
 For Others Facing This Issue: 
 Hope this helps anyone else facing similar performance bottlenecks with SAHI! 🙌  | 
  
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have high-end pc to run predictions with Cam. Since I'm getting max 3 fps at %15GPU load and 7-8%CPU load. Without SAHI at test runs I can able to get around 90fps. Is there anything I'm missing by building my structure with SAHI. Gemini says whole process waiting for SAHI to complete slices meanwhile GPU is not used. Is there any way to express to load on GPU.
Beta Was this translation helpful? Give feedback.
All reactions