New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Issue: FMeasure compute too slow for detection task #4129

Closed

eugene123tw opened this issue Nov 23, 2024 · 0 comments · Fixed by #4130

Contributor

eugene123tw commented Nov 23, 2024 •

edited

Loading

Describe the bug
FMeasure computation takes far too long for detection tasks:

func:'compute' args:[(FMeasure(),), {}] took: 83.5710 sec
func:'compute' args:[(FMeasure(),), {}] took: 124.5308 sec
func:'compute' args:[(FMeasure(),), {}] took: 88.4116 sec
func:'compute' args:[(FMeasure(),), {}] took: 92.7406 sec

Steps to Reproduce

otx train --config src/otx/recipe/detection/yolox_s.yaml --data_root /home/yuchunli/_DATASET/ADL_full_res_coco --work_dir otx-workspace/yolox_s

Environment:

OS:
Framework version:
Python version:
OpenVINO version:
CUDA/cuDNN version:
GPU model and memory:

eugene123tw linked a pull request

that will close this issue

Refactor detection FMetric #4130

Merged

8 tasks

kprokofi closed this as completed in #4130

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment