mars-project / mars-project/mars
Create a metric system for optimization
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.7k
- Forks
- 325
- PR merge metrics
- No merged PRs in 30d
Description
Information to Collect
===============
* Execution details of every job
* Data read amount (with confidence)
* Execution cost (with confidence)
* Network transfer amount (with confidence)
* Peak memory cost in execution
Information to Infer
==============
* Earliest / latest finish time of worker at a time point
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.
Research direction
The issue describes a proposed optimization metric system rather than naming files, tests, or an entry point. Begin by locating the execution and optimization components in the repository, then determine how job details, data movement, cost, memory, and worker finish times would be collected or inferred. Done means the required metrics and their confidence are defined and supported by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100