Feat/latency profiling gui evaluator#539
Closed
AdityaX18 wants to merge 2 commits intoJdeRobot:masterfrom
Closed
Conversation
Closes #ISSUE_NUMBER_HERE perceptionmetrics/cli/computational_cost.py already provided latency metrics for CLI users but the GUI evaluator showed no timing data. Changes: - perceptionmetrics/utils/latency_profiler.py: new LatencyReport class recording per-image wall-clock time via time.perf_counter(). Computes mean, median, P95, P99, FPS using stdlib only — no new dependencies. - tabs/evaluator.py: wrap inference call with perf_counter(), render 4-column Streamlit metric row (mean ms, FPS, P95, P99) after evaluation. Consistent with existing get_computational_cost() approach in the CLI.
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
2 participants
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.
Summary
Fixes #538
Problem
tabs/evaluator.pyruns inference with no timing instrumentation.perceptionmetrics/cli/computational_cost.pyalready supports latency metrics —the GUI was the only entry point missing this functionality.
Changes
perceptionmetrics/utils/latency_profiler.pyLatencyReportdataclasstabs/evaluator.pyWhat the user sees
After evaluation, a new latency metrics row appears in the GUI:
Implementation details
time.perf_counter()for high-resolution timingstatisticsImpact