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

[Discussion] Performance of cached vs non-cached geometry #106

Open
Yurlungur opened this issue Apr 19, 2022 · 0 comments
Open

[Discussion] Performance of cached vs non-cached geometry #106

Yurlungur opened this issue Apr 19, 2022 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@Yurlungur
Copy link
Collaborator

Yurlungur commented Apr 19, 2022

I went ahead and ran the torus for 100 cycles with and without cached geometry to compare performance. Cache wins... barely. Some details:

Setup

  • I used a single 256*256*256 meshblock.
  • For the cached geometry, I turned on axisymmetric.
  • I ran on a single A100 GPU.
  • I ran for 100 cycles.
  • Otherwise I used the default torus.pin input deck.

Results

  • The cached geometry ran at 5.75e7 zone-cycles/gpu-second
  • The analytic geometry ran at 4.0e7 zone-cycles/gpu-second

This translates to about a 30% speedup between cached and analytic geometries in 3D... with the cached geometry being faster.

@Yurlungur Yurlungur added the documentation Improvements or additions to documentation label Apr 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant