firemodels
Unstructured solid performance penalty when slice file output included
I have just started testing some unstructured solids problems. One thing I noticed right away was that there was a big performance penalty when I added slices to the output. In the two attached models, the one without slices ran in 7 seconds and the one with three slices ran in 43 seconds.
Sincerely, Daniel Swenson Thunderhead Engineering user_guide_unstructured_solid.fds.txt user_guide_unstructured_solid_with_slices.fds.txt
An update on this, Glenn noted that the 6x difference in run times happens in windows. Also, seems the difference is still there when swapping the geometry by an OBST of similar size.
Linux and osx difference closer to 1.5x. also difference proportional to number of slice files output and number of time steps output. I wonder if this is a file flushing issue.
On Tue, Oct 13, 2020, 4:04 PM marcosvanella [email protected] wrote:
An update on this, Glenn noted that the 6x difference in run times happens in windows. Also, seems the difference is still there when swapping the geometry by an OBST of similar size.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/firemodels/fds/issues/8838#issuecomment-707976663, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6UCRUUWQUX6KE7IV4RW4TSKSXDDANCNFSM4SNMS5RQ .
Good idea to check with an OBST. So this is probably not a practical issue, since on larger FDS 6 models slices are not a noticeable cost in the solution.
Maybe close this case?
Hi Dan, let's leave it open for now while we try to understand why we see such a difference in timings for IO between Windows and Unix systems.