Remove type instabilities and allocations #36
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #29.
Here some benchmarks (all on an AMD Ryzen Threadripper 3990X). What used to be
main loop
in the timer output is now calledcontainer_interaction
.Rectangular Tank
One Thread
On main
This PR
24 Threads
On Main
This PR
Oscillating Beam
Here, the difference is not big because we only have one type of container. The type instabilities only occur when we couple different types of containers in one simulation.
Note that the remaining allocations in the timer output are just the timers themselves (~0.026 bytes per timer).
One Thread
On main
This PR