ovperf-collector
Collect CPU, memory, and GPU metrics as time series, together with application timings, scopes, and counters. The package provides Python bindings over a native C library and can correlate collected data with Nsight Systems captures. It supports standalone use in Python and native applications.
Install
python -m pip install ovperf-collector
Python 3.10 or later is required. Native collection supports Linux x86-64 and ARM64 with glibc 2.35 or newer, and Windows 10 or later on x64. GPU metrics require a supported NVIDIA GPU and an installed NVIDIA driver; unavailable metrics are omitted. The base package has no mandatory Python dependencies.
For optional Parquet export:
python -m pip install 'ovperf-collector[parquet]'
Native SDK
Starting with 0.4.7, official Linux x86-64, Linux ARM64, and Windows x64 wheels
include a C/C++ SDK in ovperf_collector/sdk. It contains headers in include/,
CMake files in lib/cmake/ovperf_collector/, and, on Windows, the import library
lib/ovperf_collector.lib. Native applications link the packaged collector
runtime without rebuilding it or starting Python.
Set CMAKE_PREFIX_PATH to the absolute installed ovperf_collector/sdk directory.
For an existing C++ target:
find_package(ovperf_collector CONFIG REQUIRED)
target_link_libraries(my_app PRIVATE ovperf_collector::ovperf_collector)
This target requires C++17. C targets can link ovperf_collector::core instead.
Keep the SDK and shared runtime in their installed relative locations. For
deployment, make the runtime available through the application's library search
path; on Windows, placing ovperf_collector.dll beside the executable suffices.
License
The ovperf-collector implementation is licensed under Apache-2.0. Wheels include license and attribution files for incorporated third-party code and use of the official NVML build header. The header, NVIDIA driver and NVML runtime are provided separately and are not bundled with this package.
The wheel's .dist-info/licenses/THIRD-PARTY-NOTICES.txt lists the component
attributions. Its .dist-info/licenses/ directory contains the following notices.
The NVTX source is in third_party/nvtx3/ in the build source; Windows runtime
components are linked into ovperf_collector/ovperf_collector.dll.
| Component | Attribution and license | Distributed notice |
|---|---|---|
| NVTX3 | Copyright (c) 2009-2025 NVIDIA CORPORATION & AFFILIATES. All rights reserved. Apache-2.0 WITH LLVM-exception. | LICENSE-NVTX.txt, third_party/nvtx3/LICENSE.txt |
| NVML header usage | NVIDIA Corporation; official header used only to build, under the terms reproduced in its notice. | LICENSE-NVML.txt |
| MinGW-w64 runtime (Windows only) | MinGW-w64 project, Kai Tietz, Egor Duda, Keith Marshall, David M. Gay and Lucent Technologies; ZPL-2.1, public-domain and the file-specific permissive terms reproduced in the notice. | LICENSE-MINGW-W64.txt |
| LLVM compiler-rt builtins (Windows only) | LLVM Project; Apache-2.0 WITH LLVM-exception. | LICENSE-LLVM.txt |
Optional Python packages and the NVIDIA driver are installed separately; they are not included in the wheel. The license files contain the complete terms and original attributions, including the Windows file-level notices.
Contributions
This project is currently not accepting contributions.
Metadata
Release files for ovperf-collector 0.4.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ovperf_collector-0.4.7-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| ovperf_collector-0.4.7-py3-none-manylinux_2_35_x86_64.whl | Python 3 | none | Linux glibc 2.35+ x86-64 | Details |
| ovperf_collector-0.4.7-py3-none-manylinux_2_35_aarch64.whl | Python 3 | none | Linux glibc 2.35+ ARM64 | Details |
Total release size: 530.3 kB
Release files / ovperf_collector-0.4.7-py3-none-win_amd64.whl
| Download URL | ovperf_collector-0.4.7-py3-none-win_amd64.whl |
|---|---|
| Size | 186.5 kB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
a38455a4cfe6fc4ea66066b1035f3730c6f042ac2550b8992f100fb3fb37f006
|
|
BLAKE2b-256 checksum How to use checksums |
0da41807a0aea2699abd0804b4d97bc4de16a8c27e5381fdf9437c32a49870e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / ovperf_collector-0.4.7-py3-none-manylinux_2_35_x86_64.whl
| Download URL | ovperf_collector-0.4.7-py3-none-manylinux_2_35_x86_64.whl |
|---|---|
| Size | 171.4 kB |
| Tags | Linux glibc 2.35+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
48d9c881789c6c4f788b9e9243642a959e3f73fcd3ab1b5657ffd994a6da0861
|
|
BLAKE2b-256 checksum How to use checksums |
daa76064c1c26218d4ae7513ee5113fc932b245bb2fca1de8af9df48eb1b90ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / ovperf_collector-0.4.7-py3-none-manylinux_2_35_aarch64.whl
| Download URL | ovperf_collector-0.4.7-py3-none-manylinux_2_35_aarch64.whl |
|---|---|
| Size | 172.4 kB |
| Tags | Linux glibc 2.35+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
f1ff87023e25a39e575c4d1208329b20910d6effa54d78b7eb93aa27c09feca5
|
|
BLAKE2b-256 checksum How to use checksums |
090be32c4f2b9597621b184d5a3299181cf95af733b5bc044dc9fd17da991376
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for ovperf-collector 0.4.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
