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
Don't restart timer on every incoming parcel. #2031
Conversation
- added general support for startup functions and command line options in plugins
- flyby: improve error handling in create_message_handler and runtime_support_serve - flyby: exporting locality class to avoid linker problems - flyby: exporting hpx::performance_counters::detail::regex_from_pattern WIP
- moved more function declarations out of hpx_fwd.hpp - added dynamic action registration with message handlers (at startup)
@justwagle the performance counters have been implemented now (see description above). Please verify. |
The counters are working. I have attached a sample output below. There is however, an error on one of the examples if I build this branch with HPX_WITH_EXAMPLES=ON. I have listed the error below. |
The compilation error in the example was fixed here: a3d32ae. |
e2918a6
to
d041c97
Compare
- new counter: /coalescing/count/average-parcels-per-message also: - renamed the counter /coalescing/time/parcel-arrival to /coalescing/time/average-parcel-arrival - flyby: renamed counters /runtime/count/action_invocation to /runtime/count/action-invocation, and /runtime/count/remote_action_invocation to /runtime/count/remote- action-invocation to unify naming conventions for counters
d041c97
to
4df7832
Compare
Don't restart timer on every incoming parcel.
@justwagle: This solves the issue that the parcel coalescing timer was restarted for each incoming parcel. Please verify.
This PR also adds 3 performance counters which can be used to report on the message coalescing: