openvinotoolkit/openvino

[Good First Issue]: if operation is incorrectly reporting profiling data in GPU

Open

#24,244 opened on Apr 25, 2024

View on GitHub
 (25 comments) (0 reactions) (1 assignee)C++ (3,229 forks)auto 404
category: GPUgood first issueno_stale

Repository metrics

Stars
 (10,286 stars)
PR merge metrics
 (Avg merge 14d 3h) (305 merged PRs in 30d)

Description

Context

Performance counter numbers works incorrectly with if operation. Using models with if layer, the reported time is almost zero, and there is a big delta between the some of the latencies of the operations vs. the end-to-end latency reported by benchmark_app.

Counter statistics are critical for performance analysis and optimizations

Below "total time" is reported by -pc, whereas "Latency" is computed as end-to-end inference latency by benchmark_app. Counter

What needs to be done?

Fix performance counters in if operation to see adequate layer statistics

Example Pull Requests

No response

Resources

Contact points

sshlyapn, p-durandin

Ticket

No response

Contributor guide

Research direction
Investigate the performance counter implementation for the 'if' operation in the GPU plugin, identify where timing is incorrectly reported, and fix the counter logic to reflect accurate profiling data.
Tech stack
cpp
Domain
performance
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70