Move resource usage logging into instrumentation
还没有人认领这个 Issue。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- Python
- 星标
- 15
- 派生
- 22
- 平均合并
- 4 天 46 分钟
- 30 天内合并 PR
- 6
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
lowRISC/dvsim 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 84/100
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 72/100
-
Better log visibility on the license type usage profile可能已有人在做 @AlexJones0 于 9 天前认领。 未关闭
-
enhancement
难度 3/5 1-2 天 新手友好度 75/100
相似的 Issue
-
docs(types): update the collection binding note now that typed collections shipped in pycubrid 1.9.0未关闭documentation priority: low size: S
难度 2/5 1-3 小时 新手友好度 75/100
cubrid-lab/sqlalchemy-cubrid#768 ·
维护者通常 1 天内回复
-
bug help wanted
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
documentation
难度 1/5 1 小时以内 新手友好度 65/100
ansys/pydpf-core#3547 ·
维护者通常 1 天内回复
-
core
难度 2/5 1-3 小时 新手友好度 70/100
vectorize-io/hindsight#5457 ·
维护者通常 1 天内回复
-
[Bug]: LangChain drops OpenAI Responses text blocks from session recording可能已有人在做 @ktz03 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
volcengine/OpenViking#5806 ·
维护者通常 1 天内回复