feat(poi): benchmark device/precision propagation and reliability fixes#226
Merged
Conversation
- Add --resource_config CLI arg to poi_stream_density.py so DEVICE and MODEL_PRECISION are propagated through all stream-density re-init iterations (make benchmark DEVICE=all-gpu.env now works end-to-end) - Catch PermissionError in _save_alert_thumbnails: logs a clear warning instead of crashing when results/ is root-owned - Clarify true E2E latency measurement: the primary VLM metrics-file latency (e.g. 128ms) is frame capture → alert dispatch (start set via user_log_start_time with DLStreamer frame timestamp, end via log_end_time at alert dispatch). Corrects misleading comments that said the metric excluded DLStreamer pipeline latency. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
sachinkaushik
approved these changes
May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
What are you changing?
Issue this PR will close
close: #issue_number
Anything the reviewer should know when reviewing this PR?
Test Instructions if applicable
If the there are associated PRs in other repositories, please link them here (i.e. intel-retail/performance-tools )