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

1908 1909 1910 performance optimizations 1 #1916

Closed

Conversation

stmcgovern
Copy link
Contributor

Closes #1908.
Closes #1909.
Closes #1910.
First PR of multiple for fine-grained performance enhancements.

@stmcgovern stmcgovern linked an issue Aug 16, 2022 that may be closed by this pull request
3 tasks
@stmcgovern stmcgovern force-pushed the 1908-1909-1910-performance-optimizations-1 branch from dcf5234 to b189a58 Compare August 16, 2022 15:05
@github-actions
Copy link

github-actions bot commented Aug 16, 2022

Pipelines results

PR tests (gcc-12, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (gcc-5, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (clang-3.9, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (gcc-10, ubuntu, openmpi, no LB)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (clang-5.0, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (gcc-6, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (gcc-9, ubuntu, mpich, zoltan)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (clang-9, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (clang-13, alpine, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (clang-11, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (gcc-8, ubuntu, mpich, address sanitizer)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (nvidia cuda 11.0, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (clang-12, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (nvidia cuda 10.1, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (clang-14, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (intel icpx, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (clang-10, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (clang-13, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (gcc-11, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


PR tests (intel icpc, ubuntu, mpich)

Build for 5a7e810

Compilation - successful

Testing - passed

Build log


@stmcgovern stmcgovern force-pushed the 1908-1909-1910-performance-optimizations-1 branch from b189a58 to 0bad323 Compare August 16, 2022 22:14
@stmcgovern stmcgovern marked this pull request as ready for review August 16, 2022 22:16
@stmcgovern stmcgovern force-pushed the 1908-1909-1910-performance-optimizations-1 branch from 0bad323 to 5a7e810 Compare August 16, 2022 22:17
@codecov
Copy link

codecov bot commented Aug 16, 2022

Codecov Report

Merging #1916 (5a7e810) into develop (397dc80) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop    #1916   +/-   ##
========================================
  Coverage    84.39%   84.40%           
========================================
  Files          761      761           
  Lines        26866    26870    +4     
========================================
+ Hits         22673    22679    +6     
+ Misses        4193     4191    -2     
Impacted Files Coverage Δ
src/vt/configs/debug/debug_print.h 100.00% <ø> (ø)
src/vt/context/context.h 91.66% <ø> (ø)
src/vt/messaging/active.h 72.91% <ø> (ø)
src/vt/messaging/active.cc 87.01% <100.00%> (+0.10%) ⬆️
src/vt/phase/phase_manager.cc 92.56% <0.00%> (+1.35%) ⬆️

@@ -91,6 +95,7 @@
vt::config::CtxEnum::ctx, \
vt::config::ModeEnum::inmode \
>::apply(vt_debug_argument_option(cat) or force, __VA_ARGS__)
#endif
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Though it's small, I think it's preferable to put this in a separate PR, for easier traceability.

@@ -152,6 +152,10 @@ ActiveMessenger::ActiveMessenger()
};
}

void ActiveMessenger::initialize() {
comm_ = theContext()->getComm();
}
Copy link
Member

@PhilMiller PhilMiller Aug 23, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did we resolve the question of whether the communicator will always be initialized by the time this method gets called?

@@ -83,6 +83,10 @@
#define vt_debug_argument_option(opt) \
::vt::debug::preConfig()->vt_debug_ ## opt

#if vt_check_enabled(production_build)
#define vt_debug_print_impl(force, inconfig, inmode, cat, ctx, ...) \
vt_force_use(__VA_ARGS__)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
vt_force_use(__VA_ARGS__)
do { if (false) vt_force_use(__VA_ARGS__); } while (false);

@stmcgovern
Copy link
Contributor Author

Split into PR #1924, #1925, and #1926.

@stmcgovern stmcgovern closed this Aug 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants