You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there! I have used both Ultralytics and MMYOLO to run training of different models to compare performance. Running the same model (YOLOv5s) through Ultralytics takes considerably less time than training with MMYOLO. This is quite confusing when the same machine is being used to train similar models. Can somebody help me understand this?
Environment
sys.platform: linux
Python: 3.8.19 (default, Mar 20 2024, 19:58:24) [GCC 11.2.0]
CUDA available: True
MUSA available: False
numpy_random_seed: 2147483648
GPU 0: NVIDIA RTX 2000 Ada Generation Laptop GPU
CUDA_HOME: /usr/local/cuda-12.1
NVCC: Cuda compilation tools, release 12.1, V12.1.66
GCC: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
PyTorch: 2.0.0+cu117
PyTorch compiling details: PyTorch built with:
GCC 9.3
C++ Version: 201703
Intel(R) oneAPI Math Kernel Library Version 2022.2-Product Build 20220804 for Intel(R) 64 architecture applications
Prerequisite
💬 Describe the reimplementation questions
Hi there! I have used both Ultralytics and MMYOLO to run training of different models to compare performance. Running the same model (YOLOv5s) through Ultralytics takes considerably less time than training with MMYOLO. This is quite confusing when the same machine is being used to train similar models. Can somebody help me understand this?
Environment
sys.platform: linux
Python: 3.8.19 (default, Mar 20 2024, 19:58:24) [GCC 11.2.0]
CUDA available: True
MUSA available: False
numpy_random_seed: 2147483648
GPU 0: NVIDIA RTX 2000 Ada Generation Laptop GPU
CUDA_HOME: /usr/local/cuda-12.1
NVCC: Cuda compilation tools, release 12.1, V12.1.66
GCC: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
PyTorch: 2.0.0+cu117
PyTorch compiling details: PyTorch built with:
OpenCV: 4.9.0
MMEngine: 0.10.4
MMCV: 2.0.1
MMDetection: 3.3.0
MMYOLO: 0.6.0+8c4d9dc
Expected results
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: