Are you sure you want to delete this access key?
comments | description | keywords |
---|---|---|
true | Learn how to evaluate your YOLOv8 model's performance in real-world scenarios using benchmark mode. Optimize speed, accuracy, and resource allocation across export formats. | model benchmarking, YOLOv8, Ultralytics, performance evaluation, export formats, ONNX, TensorRT, OpenVINO, CoreML, TensorFlow, optimization, mAP50-95, inference time |
Once your model is trained and validated, the next logical step is to evaluate its performance in various real-world scenarios. Benchmark mode in Ultralytics YOLOv8 serves this purpose by providing a robust framework for assessing the speed and accuracy of your model across a range of export formats.
Watch: Ultralytics Modes Tutorial: Benchmark
!!! tip
* Export to ONNX or OpenVINO for up to 3x CPU speedup.
* Export to TensorRT for up to 5x GPU speedup.
Run YOLOv8n benchmarks on all supported export formats including ONNX, TensorRT etc. See Arguments section below for a full list of export arguments.
!!! example
=== "Python"
```python
from ultralytics.utils.benchmarks import benchmark
# Benchmark on GPU
benchmark(model="yolov8n.pt", data="coco8.yaml", imgsz=640, half=False, device=0)
```
=== "CLI"
```bash
yolo benchmark model=yolov8n.pt data='coco8.yaml' imgsz=640 half=False device=0
```
Arguments such as model
, data
, imgsz
, half
, device
, and verbose
provide users with the flexibility to fine-tune the benchmarks to their specific needs and compare the performance of different export formats with ease.
Key | Default Value | Description |
---|---|---|
model |
None |
Specifies the path to the model file. Accepts both .pt and .yaml formats, e.g., "yolov8n.pt" for pre-trained models or configuration files. |
data |
None |
Path to a YAML file defining the dataset for benchmarking, typically including paths and settings for validation data. Example: "coco8.yaml" . |
imgsz |
640 |
The input image size for the model. Can be a single integer for square images or a tuple (width, height) for non-square, e.g., (640, 480) . |
half |
False |
Enables FP16 (half-precision) inference, reducing memory usage and possibly increasing speed on compatible hardware. Use half=True to enable. |
int8 |
False |
Activates INT8 quantization for further optimized performance on supported devices, especially useful for edge devices. Set int8=True to use. |
device |
None |
Defines the computation device(s) for benchmarking, such as "cpu" , "cuda:0" , or a list of devices like "cuda:0,1" for multi-GPU setups. |
verbose |
False |
Controls the level of detail in logging output. A boolean value; set verbose=True for detailed logs or a float for thresholding errors. |
Benchmarks will attempt to run automatically on all possible export formats below.
{% include "macros/export-table.md" %}
See full export
details in the Export page.
Ultralytics YOLOv8 offers a Benchmark mode to assess your model's performance across different export formats. This mode provides insights into key metrics such as mean Average Precision (mAP50-95), accuracy, and inference time in milliseconds. To run benchmarks, you can use either Python or CLI commands. For example, to benchmark on a GPU:
!!! example
=== "Python"
```python
from ultralytics.utils.benchmarks import benchmark
# Benchmark on GPU
benchmark(model="yolov8n.pt", data="coco8.yaml", imgsz=640, half=False, device=0)
```
=== "CLI"
```bash
yolo benchmark model=yolov8n.pt data='coco8.yaml' imgsz=640 half=False device=0
```
For more details on benchmark arguments, visit the Arguments section.
Exporting YOLOv8 models to different formats such as ONNX, TensorRT, and OpenVINO allows you to optimize performance based on your deployment environment. For instance:
Benchmarking your YOLOv8 models is essential for several reasons:
YOLOv8 supports a variety of export formats, each tailored for specific hardware and use cases:
When running benchmarks, several arguments can be customized to suit specific needs:
Press p or to see the previous file or, n or to see the next file
Are you sure you want to delete this access key?
Are you sure you want to delete this access key?
Are you sure you want to delete this access key?
Are you sure you want to delete this access key?