Skip to content
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

APEX profile needs to be stored in the AGAS #63

Open
khuck opened this issue Apr 24, 2016 · 1 comment
Open

APEX profile needs to be stored in the AGAS #63

khuck opened this issue Apr 24, 2016 · 1 comment

Comments

@khuck
Copy link
Collaborator

khuck commented Apr 24, 2016

For HPX and HPX-5 implementations, the profile_listener object should replicate the current local state from each locality into the HPX AGAS, and provide mechanisms for the policies to extract remote locality APEX state from other localities. This would provide built-in globally-aware support.

The initial thought is that when the profiler listener finishes processing the current profiler queue (or after N profiler objects are processed, whichever comes first) the current profile state would be replicated in the HPX AGAS. Could be replicated periodically also/instead.

I'm not sure how this would be supported for other runtimes (i.e. MPI+X).

For OCR, this would be similar to HPX.

This code should live in the respective runtime glue-code - in HPX3, that's easy because we can implement it in the XPRESS-APEX code that will be submoduled into the HPX project. HPX-5 already has some code for performing something similar, we should modify that to implement this for HPX-5.

@khuck
Copy link
Collaborator Author

khuck commented Apr 25, 2016

Nick reminded me that this is already supported using the counter framework in HPX3. Assuming that code isn't rusty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant