Move resource usage logging into instrumentation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Read the linked issue #267 and PR #268, especially the discussion suggesting a ResourceInstrumentation class. The issue says the existing per-resource job-status logging should move into that class, but notes that the change was not straightforward; first trace where that logging is currently implemented and how instrumentation is structured. Done means the status data is available through instrumentation for producing reports at the end of runs.
Written by the indexing model from the issue text.
Description
A previous issue and PR were made (here https://github.com/lowRISC/dvsim/issues/267 and here https://github.com/lowRISC/dvsim/pull/268) to log per resource, the number of jobs for each status. For example, for the simulation tool Xcelium, how jobs are scheduled, queued, running, etc.
In the following https://github.com/lowRISC/dvsim/pull/268#discussion_r4186087377, @AlexJones0 suggested this logic could be moved into a ResourceInstrumentation class. This would have some advantages, such as making it easy to pull the data and produce other reports at the end of runs. I looked into this while addressing the comments in the linked PR, but found it wasn't overly straightforward. I deferred it for now, but in the long run it would be a good change to make.
- Dominant language
- Python
- Stars
- 15
- Forks
- 22
- Avg merge
- 4d 46m
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 lowRISC/dvsim
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Better log visibility on the license type usage profilePossibly taken @AlexJones0 claimed this 8 days ago. Open
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 75/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Graphify-Labs/graphify#4241 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
DeviceTrackerOpen
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
XiaoMi/ha_xiaomi_home#1821 ·
Maintainers usually reply within 1 day
-
Maven path-index: "Ambiguous or noncanonical artifact path" error does not report the offending pathOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pulp/pulp_maven#524 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day