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
Support Checkpointing Components #3159
Conversation
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.
Very nice! Thanks!
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.
Serialization of futures should be handled correctly. This will also require to implement something like we have for parcels.
I looked through the code we have to see what we can do to come to a mutually acceptable solution for this. I think we can create a specialization for |
What's the status of this PR? |
@msimberg this still needs some work on the serialization end. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed. Please re-open if necessary. |
Let's keep this open for now This is needed functionality. |
78b1250
to
9ec815c
Compare
9ec815c
to
4803e7c
Compare
- Fixed checkpoint.cpp to make floats constant -> Makes msvs happy - Adding checkpoint_component.cpp - Raise abstraction level in checkpoint -> Create new function arch_data that will be overloaded to properly handle components - Adding in components to test - Working component checkpointing! -> Checkpoints a server -> Still needs to create a new client - Create new client on restored server - Adding functionality to enable checkpointing of clients -> Checkpoints the server the client points to -> Still need to add functionality to restore which would create a new client with the resurrected server - Allowing components to be restored with provided client -> Users can now use clients to checkpoint and restore servers - Updating Documentation - Preparing unit test for checkpointing components - Fixing 1d_stencil_4_checkpoint example for Win/Mac - Fixing compilation on gcc - Adding documentation for checkpointing components - Clean up code with Clang-Format -> Update year on license
- Created `prep` function to handle clients - Ensures `get_id` will be ready - Passes future of `get_prt` to dataflow - Removes a "bad example" from `checkpoint_component.cpp` - Adding headers for for inspect
- flyby: transferring old documentation
4803e7c
to
4d1252d
Compare
This should be good to go now. Please review. |
LGTM! |
The errors on pycicle are unrelated. |
Extended current implementation of
hpx::util::checkpoint
to properly handle components.Summary:
checkpoint.cpp
to make floats constantcheckpoint_component.cpp
handle components
create a new client with the resurrected server
servers