TimelyDataflow / TimelyDataflow/timely-dataflow

ProgressEvent's messages and internal fields

Open
#286 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
3.6k
Forks
293
Avg merge
14h 46m
Merged PRs (30d)
4

Description

Hi Frank!

For profiling progress & visualizing dataflow frontiers, I believe I need some information in ProgressEvents on what kind of progress actually happened. I think that the messages and internal fields could help me with that [1].

Currently they are only mocked up in send(...) and receive(...). I'd be happy to create a PR and implement them, if you can guide me a little on what the Vec fields are supposed to be. E.g., what are target and source descriptor in this context (I assume they are the first two usize coordinates in the Vec's tuples)?

Cheers,
Malte

[1]

pub struct ProgressEvent {
    ...
    /// List of message updates, containing Target descriptor, timestamp as string, and delta.
    pub messages: Vec<(usize, usize, String, i64)>,
    /// List of capability updates, containing Source descriptor, timestamp as string, and delta.
    pub internal: Vec<(usize, usize, String, i64)>,
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing ProgressEvent and the send(...) and receive(...) paths, where the messages and internal fields are currently mocked up. Clarify the meanings of the Vec tuple coordinates, including source and target descriptors, before implementing the updates; done means these fields accurately report message and capability progress for profiling.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.