-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Nutils cases are extremely slower than the rest #506
Comments
IIRC installing mkl should held to some extend. Then, Nutils picks a different solver backend. Note that the If we find anything quick and simple, OK, but I would not want to change the numerics here. For the systemtests, I would simply compute a few timesteps. |
There is already #429 which touches the case quite a bit. |
Update: @uekerman wanted to have a closer look into the numerics, but after the currently semi-done release cycle. |
The participant micro-nutils in the two-scale heat conduction tutorial is also extremely slow compared to other micro simulations of similar kind, and I have a feeling that the numerics there has a lot of potential for improvement. |
As stated in the Nutils Book, Nutils is not (yet) the fastest tool in its class. I experience that in our perpendicular-flap tutorial, where especially our
fluid-nutils
case is taking orders of magnitude longer than the rest of the solvers (half a day instead of a couple of minutes).Following the official suggestions, I tried something like
without a directly visible impact (did not measure). I also commented-out the VTK output at the end of each coupling time window.
However, I think that we should first have a closer look and check if we are doing any extremely unnecessary work (e.g., too tight convergence measures, too much output, etc). The mesh already seems to be very coarse.
@gertjanvanzwieten @uekerman do you maybe have any quick ideas?
If we could drop the simulation time to a couple of minutes (or anything less than an hour), we could also integrate this in our system tests.
The text was updated successfully, but these errors were encountered: