-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Compile time - runtime separation / single node multiple GPU milestones #6359
Comments
https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/operators/while_op.cc#L49 |
We don't have method of removing objects from protobuf |
so we need some helper function to help modify the execution plan proto message. |
The current attribute can be serialized. https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/framework/op_desc.cc#L296 |
Need a Parallel Operator to execute the block with multi threads. |
This issue is out-of-date, closing. |
Attributes use Attr proto message only (any C++ trick to make changing to it easier?):
The current attribute items can't be serialized, we can't use ProgramDesc for executor unless we change this.
C++ Executor take ProgramDesc
Eventually we will change to ExecutionPlan, ProgramDesc is similar to ExecutionPlan (both can be serialized), but ProgramDescBind is too different from ExecutionPlan. If we develop multiple thread executor based on ProgramDescBind, there are too much to change later.
ExecutionPlan design doc (Add ExecutionPlan design. #6078)
change C++ Executor to take ExecutionPlan
Multiple thread executor design doc
C++ multiple thread Executor
simple C++ planner
Just place everything on CPU / GPU-0
Modular Python Executor
current code:
single node multiple GPU planner
Dependency
The text was updated successfully, but these errors were encountered: