fix(enhancement): Added per stream fps threshold logic

[rishika-y-gaur]

Evaluate stream density per camera target FPS so mixed-camera ASC bundles stop only when each stream meets its own threshold.

Resolves: #235

PR Checklist

• Added label to the Pull Request for easier discoverability and search
• Commit Message meets guidelines as indicated in the URL https://github.com/intel-retail/performance-tools/blob/main/CONTRIBUTING.md
• Every commit is a single defect fix and does not mix feature addition or changes
• Unit Tests have been added for new changes
• Updated Documentation as relevant to the changes
• All commented code has been removed
• If you've added a dependency, you've ensured license is compatible with repository license and clearly outlined the added dependency.
• PR change contains code related to security
• PR introduces changes that breaks compatibility with other modules (If YES, please provide details below)

What are you changing?

This PR updates stream-density stopping logic to use per-stream target FPS, so mixed-camera ASC bundles stop only when each stream meets its own threshold.

Issue this PR will close

close: #235

Anything the reviewer should know when reviewing this PR?

Per-stream pass/fail thresholds with hysteresis are now used instead of a single shared FPS target, and target FPS thresholds are taken from camera config JSON files.

Test Instructions if applicable

• Use a camera config with different targetFps values per camera.
• Run stream density benchmark.
• Confirm each stream is checked against its own threshold before stopping.

If the there are associated PRs in other repositories, please link them here (i.e. intel-retail/performance-tools )

[Copilot]

Pull request overview

This PR updates the stream-density benchmark’s stopping/scaling logic so mixed-camera bundles are evaluated against per-stream target FPS thresholds (derived from a camera config JSON), rather than using one shared FPS target for all streams.

Changes:

• Add camera-config JSON parsing to build a per-stream targetFps map.
• Update pass/fail + hysteresis evaluation to use per-stream thresholds.
• Adjust increment estimation to use an aggregate (mean) of per-stream targets.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (1)

benchmark-scripts/stream_density.py:91

• re.compile(...) runs on every call to build_per_stream_target_fps, even though the comment says it’s compiled once. Since this function is invoked every sampling window, cache the compiled regex (similar to the config cache) to avoid repeated compilation overhead.

    # Compile regex once (if needed for stream name parsing)
    stream_pattern = re.compile(r"pipeline_stream(\d+)")
    per_stream_targets = {}

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

benchmark-scripts/stream_density.py:90

• The comment says "Compile regex once" but the regex is compiled on every call to build_per_stream_target_fps, which can be misleading when diagnosing performance behavior.

    # Compile regex once (if needed for stream name parsing)
    stream_pattern = re.compile(r"pipeline_stream(\d+)")