Open ruisearch42 opened 3 weeks ago
The end user may have an impression that type hint is applied to a DAG node, as opposed to the edge between DAG nodes/tasks.
This might be partially due to that the way we name the variables in DAG construction, e.g.,
dag = sender.send.bind(shape, dtype, inp) dag = dag.with_type_hint(TorchTensorType(shape, dtype, transport="nccl")) dag = receiver.recv.bind(dag)
The semantics becomes clearer if we have:
output = sender.send.bind(shape, dtype, inp) output_decorated = output.with_type_hint(TorchTensorType(shape, dtype, transport="nccl")) dag = receiver.recv.bind(output_decorated)
However, the API can potentially be improved to make it more intuitive. Say having something like:
sender.send.bind(inp, channel=‘nccl’)
cc: @woshiyyya
No response
I added the accelerated-dag tag
accelerated-dag
Description
The end user may have an impression that type hint is applied to a DAG node, as opposed to the edge between DAG nodes/tasks.
This might be partially due to that the way we name the variables in DAG construction, e.g.,
The semantics becomes clearer if we have:
However, the API can potentially be improved to make it more intuitive. Say having something like:
cc: @woshiyyya
Use case
No response