Skip to content

Update OpenVINO benchmarks pics#154

Open
lakshanthad wants to merge 3 commits intomainfrom
openvino-overview-benchmarks
Open

Update OpenVINO benchmarks pics#154
lakshanthad wants to merge 3 commits intomainfrom
openvino-overview-benchmarks

Conversation

@lakshanthad
Copy link
Copy Markdown
Contributor

@lakshanthad lakshanthad commented May 7, 2026

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

Refreshes the OpenVINO benchmark images in ultralytics/assets to keep documentation visuals current and aligned with the latest benchmark outputs. 📈🖼️

📊 Key Changes

  • Updated OpenVINO benchmark image assets used in documentation.
  • Replaced several optimized .avif files for OpenVINO ecosystem and hardware-specific benchmark visuals.
  • Includes refreshed benchmark graphics for Intel Ultra 7 155H CPU/GPU and Ultra 7 258V CPU/GPU results.

🎯 Purpose & Impact

  • Keeps published OpenVINO benchmark visuals accurate and up to date for readers.
  • Improves consistency between benchmark results and the documentation that references them.
  • Helps users make better-informed export and deployment comparisons based on the latest visuals.
📋 Skipped 5 files (lock files, generated, images, etc.)
  • docs/openvino-ecosystem.avif
  • docs/openvino-ultra7-155H-cpu.avif
  • docs/openvino-ultra7-155H-gpu.avif
  • docs/openvino-ultra7-258V-cpu.avif
  • docs/openvino-ultra7-258V-gpu.avif

@lakshanthad lakshanthad self-assigned this May 7, 2026
@lakshanthad lakshanthad requested a review from glenn-jocher May 7, 2026 02:57
@UltralyticsAssistant UltralyticsAssistant added documentation Improvements or additions to documentation exports Model exports (ONNX, TensorRT, TFLite, etc.) priority: low Low urgency; can wait behind higher-priority work. labels May 7, 2026
@UltralyticsAssistant
Copy link
Copy Markdown
Member

👋 Hello @lakshanthad, thank you for submitting a ultralytics/assets 🚀 PR! This is an automated message to help with review, and an engineer will assist you shortly. Please review the checklist below to help ensure a smooth merge 😊

  • Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
  • Synchronize with Source: Confirm your PR is synchronized with the ultralytics/assets main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
  • Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
  • Update Documentation: Update the relevant documentation for any new or modified features.
  • Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
  • Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
  • Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

Copy link
Copy Markdown
Member

@UltralyticsAssistant UltralyticsAssistant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔍 PR Review

Made with ❤️ by Ultralytics Actions

All 5 changed files are generated/vendored (skipped review)

📋 Skipped 5 files (lock files, generated, images, etc.)
  • docs/openvino-ecosystem.avif
  • docs/openvino-ultra7-155H-cpu.avif
  • docs/openvino-ultra7-155H-gpu.avif
  • docs/openvino-ultra7-258V-cpu.avif
  • docs/openvino-ultra7-258V-gpu.avif

Copy link
Copy Markdown

@adrianboguszewski adrianboguszewski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

258V NPU is missing

@glenn-jocher
Copy link
Copy Markdown
Member

@lakshanthad can you add 258V NPU per Adrian's request?

@lakshanthad
Copy link
Copy Markdown
Contributor Author

It is done! @glenn-jocher
cc: @adrianboguszewski

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

Labels

documentation Improvements or additions to documentation exports Model exports (ONNX, TensorRT, TFLite, etc.) priority: low Low urgency; can wait behind higher-priority work.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants