-
Notifications
You must be signed in to change notification settings - Fork 11
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
Targets for jitting #49
Labels
enhancement
New feature or request
Milestone
Comments
Here's an updated profile from a longer run (10 full timesteps on a domain sized for a real simulation). I am working on jitting several of these targets now.
|
This is really outdated. If someone is interested in reevaluating the speed after #133 is merged, that could be helpful, but this issue is not. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To be more specific than #1, I reprofiled the code using #36. I found that after increasing the number of water iterations (see #48), a few new targets for jitting seem promising.
self.free_surf()
which is called every iteration to calculate where the free surface is based on the tracks of the parcels.self.finalize_water_iteration()
which smooths the surface, among other things.self.mud_route()
andself.sand_route()
Some parts of these have been jitted, but there's still quite a lot of good optimization that could be done..flatten()
takes up a weirdly long time. Maybe arrays should just be configured to be flat 1D vectors from the get go, so that we don't have to do this reshaping all the time.Detailed profile:
The text was updated successfully, but these errors were encountered: