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

fix allocations of P4estMesh2D BCs #1636

Merged
merged 2 commits into from
Sep 13, 2023
Merged

Conversation

ranocha
Copy link
Member

@ranocha ranocha commented Sep 12, 2023

Closes #1635

@ranocha ranocha added the performance We are greedy label Sep 12, 2023
@github-actions
Copy link
Contributor

Review checklist

This checklist is meant to assist creators of PRs (to let them know what reviewers will typically look for) and reviewers (to guide them in a structured review process). Items do not need to be checked explicitly for a PR to be eligible for merging.

Purpose and scope

  • The PR has a single goal that is clear from the PR title and/or description.
  • All code changes represent a single set of modifications that logically belong together.
  • No more than 500 lines of code are changed or there is no obvious way to split the PR into multiple PRs.

Code quality

  • The code can be understood easily.
  • Newly introduced names for variables etc. are self-descriptive and consistent with existing naming conventions.
  • There are no redundancies that can be removed by simple modularization/refactoring.
  • There are no leftover debug statements or commented code sections.
  • The code adheres to our conventions and style guide, and to the Julia guidelines.

Documentation

  • New functions and types are documented with a docstring or top-level comment.
  • Relevant publications are referenced in docstrings (see example for formatting).
  • Inline comments are used to document longer or unusual code sections.
  • Comments describe intent ("why?") and not just functionality ("what?").
  • If the PR introduces a significant change or new feature, it is documented in NEWS.md.

Testing

  • The PR passes all tests.
  • New or modified lines of code are covered by tests.
  • New or modified tests run in less then 10 seconds.

Performance

  • There are no type instabilities or memory allocations in performance-critical parts.
  • If the PR intent is to improve performance, before/after time measurements are posted in the PR.

Verification

  • The correctness of the code was verified using appropriate tests.
  • If new equations/methods are added, a convergence test has been run and the results
    are posted in the PR.

Created with ❤️ by the Trixi.jl community.

@DanielDoehring
Copy link
Contributor

Maybe it makes sense to adapt the 3D case

function calc_boundary_flux!(cache, t, boundary_condition, boundary_indexing,
mesh::P4estMesh{3},
equations, surface_integral, dg::DG)

also correspondingly (also allocations are not yet observed)

function calc_boundary_flux!(cache, t, boundary_condition::BC, boundary_indexing,
                             mesh::P4estMesh{3},
                             equations, surface_integral, dg::DG) where {BC}

Similarly, one could also add this to

function calc_boundary_flux!(flux, u, t, operator_type, boundary_conditions,
mesh, equations, dg::DGMulti, cache, cache_parabolic)

function calc_boundary_flux!(cache, t, boundary_conditions, mesh,
have_nonconservative_terms, equations, dg::DGMulti)

function calc_boundary_flux!(cache, t, boundary_conditions,
mesh::Union{UnstructuredMesh2D, P4estMesh, T8codeMesh},
equations, surface_integral, dg::DG)

@codecov
Copy link

codecov bot commented Sep 12, 2023

Codecov Report

Patch coverage: 100.00% and project coverage change: -2.14% ⚠️

Comparison is base (27d4fd1) 92.94% compared to head (b3f4349) 90.80%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1636      +/-   ##
==========================================
- Coverage   92.94%   90.80%   -2.14%     
==========================================
  Files         416      416              
  Lines       34065    34100      +35     
==========================================
- Hits        31661    30963     -698     
- Misses       2404     3137     +733     
Flag Coverage Δ
unittests 90.80% <100.00%> (-2.14%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed Coverage Δ
src/solvers/dgsem_p4est/dg_2d.jl 97.51% <100.00%> (ø)

... and 72 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@ranocha
Copy link
Member Author

ranocha commented Sep 13, 2023

Thanks for your quick review! I checked the places you mentioned before submitting this PR. They do not need any treatment since they don't trigger Julia's heuristic to avoid specialization.

@ranocha ranocha merged commit bc67361 into main Sep 13, 2023
30 of 32 checks passed
@ranocha ranocha deleted the hr/fix_p4est_bc_allocations branch September 13, 2023 07:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance We are greedy
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allocations in calc_boundary_flux! on P4est meshes
2 participants