Closed GoogleCodeExporter closed 9 years ago
We'll take a look at the case.
Original comment by mcgra...@gmail.com
on 21 Jul 2009 at 4:50
Thank you very much for your answer, I wait with impatience for your answer.
Original comment by raoul.de...@gmail.com
on 22 Jul 2009 at 7:23
[deleted comment]
Well, the solution might be FDS version 5.4.0. FDS+Evac (5.3.1 and older ones)
uses
quite much memory for the evacuation meshes. But the latest source code on the
SVN
repository has already the "less memory for evacuaton meshes" fix. So, if you
can not
wait until the official release of FDS 5.4, then you should compile FDS by
yourself.
The other option is to use the win64 (for Windows 64 bit systems), if you have a
Windows machine with 64 bit operating system. Or run FDS in some Linux/Unix
machine
where you have 64 bit OS and enough memory.
TimoK
Original comment by tkorh...@gmail.com
on 3 Aug 2009 at 10:10
The FDS 5.4 consumes much less memory for the evacuation calculation,
so this issue is fixed.
Original comment by tkorh...@gmail.com
on 24 Sep 2009 at 9:36
Well, we are now already FDS 5.4.2, so I'll change this to "Verified". The FDS
5.4.2
uses less memory for the evacuation meshes than FDS 5.3.
fds5.4.0, svn3895:
fire + evac: 616 472 K RAM (Peak Memory usage, winXP32, test1)
no fire + evac: 556 404 K RAM (Peak Memory usage, winXP32, test2)
fire + no evac: 63 596 K RAM (Peak Memory usage, winXP32, test0)
fds5.4.2, svn5104:
fire + evac: 224 324 K RAM (Peak Memory usage, winXP32, test1)
no fire + evac: 162 808 K RAM (Peak Memory usage, winXP32, test2)
fire + no evac: 65 952 K RAM (Peak Memory usage, winXP32, test0)
TimoK
Original comment by tkorh...@gmail.com
on 23 Nov 2009 at 8:13
Original issue reported on code.google.com by
raoul.de...@gmail.com
on 21 Jul 2009 at 3:14