-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add documention for send/recv OP #7904
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,68 @@ | ||
# Send and Recv OP | ||
|
||
With PaddlePaddle Fluid, the node to node communication is done | ||
through the send and recv OP. The send and recv OP will be | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "will be" is passive. Please try not to use passive voices. |
||
automatically added to | ||
the | ||
[`ProgramDesc`](https://github.com/PaddlePaddle/Paddle/blob/develop/doc/design/program.md#blockdesc-and-programdesc) by | ||
the | ||
[distributed transpiler](https://github.com/PaddlePaddle/Paddle/blob/develop/doc/design/dist_refactor/distributed_architecture.md#distributed-transpiler) when | ||
a local training `ProgramDesc` is transpiled to the distributed | ||
training `ProgramDesc`. | ||
|
||
|
||
## Send OP | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Send Op => The Send Operator |
||
|
||
The send OP sends its input tensors to one or multiple recv OPs and | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I think it's not only tensor, but also SelectedRows and in fact, send op could send all kinds of variable which implement the Serialize and Deserialize interface, but now, it only supports LodTensor and SelectedRows. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It seems that Send is a broadcasting operation, as you said it could send tensors to more than one recv operators? Is a broadcasting send operator what we want? |
||
then fetches its output tensors from the recv OPs. | ||
|
||
|Input|Description| | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we need tables here? |
||
|------|------| | ||
|X|Input tensor to be sent| | ||
|
||
|Output|Description| | ||
|------|------| | ||
|Out|Output tensor to be received from the recv OP| | ||
|
||
|Attribute|Description| | ||
|------|------| | ||
|endpoints|Endpoints to send the variables to| | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would this be a list of OPs or just a list of receive OP endpoints ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's a list of receive OP endpoints. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. And receive OP endpoints is basically the parameter_server endpoints, right ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, they are the same. |
||
|epmap|Endpoints in the order of input variables, used for sharding| | ||
|
||
|
||
## Recv OP | ||
|
||
The recv OP receives its input tensors, runs the optimization block, and | ||
serves the tensors requested by the send OP. | ||
|
||
|Input|Description| | ||
|------|------| | ||
|RX|Input tensor to be received| | ||
|
||
|Attribute|Description| | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Where in this setup does the receive OP get the list of tensors as an input from send OP ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The input of send of will be the same as the input of recv op, if there is only 1 recv op. They are all setup by the transpiler. Currently there is one send op per trainer, and one recv op per pserver. We will move to one send/recv pair per parameter in the future. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks so much, that helps! |
||
|------|------| | ||
|endpoint|IP address to listen on| | ||
|OptimizeBlock|The block to run after receiving the tensors from the send OP| | ||
|ParamList|gradient to parameter name mapping to find which parameters to optimize| | ||
|GradList|parameter name to gradient name mapping to find which gradient to use| | ||
|Fanin|Number of send OPs connected to this recv OP| | ||
|
||
|
||
## Example | ||
|
||
|
||
<img src="images/send_recv.png"/> | ||
|
||
The graph above shows one iteration of the optimization process: | ||
|
||
1. When the execution reaches the send OP, it will send `A grad` and | ||
`B grad` using gRPC to the recv OPs on Pserver 0 and Pserver 1 | ||
respectively. | ||
|
||
1. After receiving the tensor, the recv OP will execute the | ||
optimization block. The optimization block on Pserver 0 will update | ||
`A` using `A grad`. Same for Pserver 1. | ||
|
||
1. The send OP will wait for the completion of the optimization | ||
block. Upon completion, it will fetch the updated `A` and `B` from | ||
the Pservers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OP => operator