Need api to have option to pass down timestamps for cpu profiles
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- api, performance
Research direction
The issue names no files, tests, or entry points. Start by locating the public CPU profiling API and its timestamp-handling documentation, then clarify the accepted units and epoch for QPC and GPU-correlated timestamps. Done means callers can pass recorded timestamps through the API and PIX can consume them for Vulkan CPU profiling.
Written by the indexing model from the issue text.
Description
The problem is that apps already have timing callbacks which have recorded timings. But there is no way to pass these into the api. For a vulkan app, that can only do cpu profiling, there is no way to pass through the timestamps or gpu correlated timestamps to PIX. My understanding is that PIX hides the timestamps because it's trying to correlate it's own gpu and cpu timestamps. But that API should be exposed.
Callers can do QPC and then hand down the timestamp, although in my app, we convert QPC * (1/QPF) = double time in seconds. Also Vulkan apps can correlate gpu timestamps, and then hand those in QPC epoch.
- Dominant language
- C++
- Stars
- 104
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/PixEvents
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
ABI: CPU timeline only `PIXBeginEvent`, `PIXEndEvent` and `PIXSetMarker` are not exported in DLLOpen
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
All issues in microsoft/PixEvents
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
shadps4-emu/shadps4-qtlauncher#453 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/differential-privacy#516 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
plengauer/DXGIOutputDuplication#76 ·
Maintainers usually reply within 1 day
-
Feature
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Narezzurri/OpenVPN-Config-Manager#95 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rhalbersma/xstd-bits#314 ·
Maintainers usually reply within 1 day