Hi @alexandrebenoit
I wasn't directly involved with the deploy of yolov10 on RVC2, but as far as I understand:
The entire architecture (both head, and middle) uses element-wise operations, which can't be optimized for the RVC2. No significant reparametrization tricks (like .fuse()) are available to mitigate the issue.
numbers:
416x416 - 24FPS, 41ms latency
640x640 - 12FPS, 86ms latency
Thanks,
Jaka