search

TNTWEN / OpenVINO-YOLOV4

This is implementation of YOLOv4,YOLOv4-relu,YOLOv4-tiny,YOLOv4-tiny-3l,Scaled-YOLOv4 and INT8 Quantization in OpenVINO2021.3
MIT License
239 stars 66 forks source link

FPS of YoloV4 tiny is slower than Yolo3 tiny #17

Closed at1993 closed 3 years ago

at1993 commented 4 years ago

@TNTWEN , thanks for the great work. I was able to convert and run the yolov4 tiny using the object_detection_demo_yolov3_async demo program. I've noticed that this new model is 10fps slower than yolov3 tiny. Then I realized the model is using data type FP32 vs FP16 in yolov3 tiny ( file size: 23MB vs 16.8MB). Is there a way to convert it to FP16? Thanks.

TNTWEN commented 4 years ago

Hello! @at1993 Thanks for your trying! https://github.com/TNTWEN/OpenVINO-YOLOV4/issues/10,

10、FP32 ,FP16 The default precision is FP32,if you want to use FP16 ,add --data_type FP16 when you run mo.py

python "C:\Program Files (x86)\IntelSWTools\openvino_2020.4.287\deployment_tools\model_optimizer\mo.py" --input_model frozen_darknet_yolov4_model.pb --transformations_config yolo_v4_tiny.json --batch 1 --reverse_input_channels --data_type FP16

TNTWEN commented 4 years ago

https://github.com/TNTWEN/OpenVINO-YOLOV4/issues/5 For intel GPU,FP16 is more suitable than FP32

at1993 commented 4 years ago

Thank you. Yes I agree that FP16 is better on intel GPU. I did try the conversion today with --data_type PF16 however, file size did not changed compared to PF32 (should be half the size right?). I thought maybe I've overlooked something.

at1993 commented 4 years ago

@TNTWEN , I did a few tests. Slightly faster. About 4-5 fps.