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

Walberla performance tracking ticket #4989

Open
6 tasks
RudolfWeeber opened this issue Aug 27, 2024 · 1 comment
Open
6 tasks

Walberla performance tracking ticket #4989

RudolfWeeber opened this issue Aug 27, 2024 · 1 comment

Comments

@RudolfWeeber
Copy link
Contributor

RudolfWeeber commented Aug 27, 2024

  • more selective ghost communication LB: avoid double communicaiton #4921
  • Use AVX vectorization in all kernels (streaming, boundaries, reset force, ...). (It might be useful to automate the generatoin of kernel_traits.hpp, first (Simplify work with walberla kernels #4988)
  • replace
  • switch to pull scheme and use combined stream-collide sweep (postponed, as I couldn't get our patched bounce back boundary condiont working with pull scheme)
  • Generate the packinfos using PyStencils and use vectorization (currently, we use hand-written pack infos form Walberla propper). In particular, do such generated packinfos outperform the currenty used memcpy pack info on the GPU
  • Multi-GPu simulatoin with cCuda-aware MPI
@jngrad jngrad changed the title Walberla performance trcking ticket Walberla performance tracking ticket Aug 27, 2024
@RudolfWeeber
Copy link
Contributor Author

Just realized that we did not yet vectorize the streaming kernel. This is probably a relatively low hanging fruit for performance on CPU.

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

No branches or pull requests

1 participant