show advantages of simulation over profiling
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- documentation, performance
Research direction
Review the current examples in the cpp-performance-profiling course and compare what simulation records with what sampling exposes. Add examples or scenarios where simulation provides information unavailable from sampling; done means the examples clearly demonstrate that advantage.
Written by the indexing model from the issue text.
Description
- deterministic and records all events
- but no advantage over just sampling in the current examples
- would be nice to add examples / scenarios where it provides something you can't get with sampling
- (thanks for the suggestion from the feedback forms)
- Dominant language
- C++
- Stars
- 11
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 ssciwr/cpp-performance-profiling
-
update profilerOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
add gpu exampleOpenenhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in ssciwr/cpp-performance-profiling
Similar issues
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gavinlouuu-kpt/mib-studio-qt#517 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
EchoTools/nevr-runtime#116 ·
Maintainers usually reply within 1 day