Lower bound on kernel execution time
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- ai-infra-agents, performance
Research direction
Reproduce the reported timing with the empty kernel and the kernel() and wait() calls described in the issue. Trace the XRT execution path involved in launching and waiting for a kernel, then document whether the overhead is expected and identify any supported option or limitation; no source file or test is named.
Written by the indexing model from the issue text.
Description
Hello developers,
While creating a very simple kernel using MLIR-AIE and testing it, I noticed a kind of lower bound on the kernel execution time, using XRT. I measured the time difference between the end of computation of my kernel and the start, and I get around 60 microseconds (so the function kernel() and wait())
Because I was not satisfied by this time, I created an "empty" kernel, doing nothing and moving no data. Using always XRT to call the kernel, I did the same computation to find the time for the kernel to run, and I found something like 45 microseconds.
My questions are
is it normal to have this overhead?
If yes, what are the option? Because actually, my CPU runs my computation faster then, and the NPU would be no need.
Thanks!
- Dominant language
- C++
- Stars
- 686
- Forks
- 549
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 70
Contributor 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 Xilinx/XRT
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 70/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·