You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Benchmark, profile and optimize interactions on GPUs.
Avoid synchronization. For example, fluid-solid and solid-solid interactions have no race conditions, so all *-solid interaction kernels can be spawned on the GPU without synchronization. The same holds for all *-fluid and *-boundary interactions. However, this should happen after optimization, since we will lose timers for each individual interaction. Also, we will only see a benefit for multi-physics simulations, as a simple fluid-boundary simulation can't run any two non-trivial interactions without synchronization. Note that a single fluid-* kernel might also be able to improve performance.
The text was updated successfully, but these errors were encountered:
efaulhaber
changed the title
Road to TrixiParticles.jk on GPUs
Road to TrixiParticles.jl on GPUs
Apr 2, 2024
Array{ELTYPE, 2}
to type parameters.Make array types in structs generic #486
Semidiscretization
object to GPU types with Adapt.jl.Recursively convert (adapt)
Semidiscretization
object to GPU types with Adapt.jl #492GPUSystem
to determine if a system is stored on the CPU or GPU #532Two alternatives: Either Minimally invasive GPU implementation with KernelAbstractions.jl without neighborhood search #493 using plain kernels for everything or Rewrite
@threaded
macro to work with GPUs #534 hiding the kernels in the@threaded
macro.SolutionSavingCallback
work on GPUs (MakeSolutionSavingCallback
work on GPUs #579).The text was updated successfully, but these errors were encountered: