natas_hw
/
openvino
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
openvino/tools/benchmark_tool
History
Jacek Pawlak 239466ca5d
copyright year update (#23370) 
New PR due to merge
conflicts(https://github.com/openvinotoolkit/openvino/pull/22917)

Updated the copyright year from 2018-2023 to 2018-2024 in all openvino
files

Ref. to script: CVS-101144

Command used:
```bash
git grep -lz '2018-2023 Intel Corporation' | xargs -0 sed -i '' -e 's/2018-2023 Intel Corporation/2018-2024 Intel Corporation/g'
```
 		2024-03-14 09:37:02 +00:00
..
openvino copyright year update (#23370) 2024-03-14 09:37:02 +00:00
CMakeLists.txt copyright year update (#23370) 2024-03-14 09:37:02 +00:00
README.md [DOCS] Docs file structure update with fixes (#23343) 2024-03-11 17:05:58 +00:00
benchmark_app.py copyright year update (#23370) 2024-03-14 09:37:02 +00:00
requirements.txt Don't require opencv-python for benchmark_app (#18565) 2023-07-15 13:00:29 +04:00
setup.py copyright year update (#23370) 2024-03-14 09:37:02 +00:00

README.md

Benchmark Python Tool

This page demonstrates how to use the Benchmark Python Tool to estimate deep learning inference performance on supported devices.

NOTE: This page describes usage of the Python implementation of the Benchmark Tool. For the C++ implementation, refer to the Benchmark C++ Tool page. The Python version is recommended for benchmarking models that will be used in Python applications, and the C++ version is recommended for benchmarking models that will be used in C++ applications. Both tools have a similar command interface and backend.

For more detailed information on how this sample works, check the dedicated article

Requriements

The Python benchmark_app is automatically installed when you install OpenVINO Developer Tools using PyPI Before running benchmark_app, make sure the openvino_env virtual environment is activated, and navigate to the directory where your model is located.

The benchmarking application works with models in the OpenVINO IR (model.xml and model.bin) and ONNX (model.onnx) formats. Make sure to convert your models if necessary.