Re: Report on Improving Speed

[Daniel Wheeler]

On Jun 9, 2006, at 2:24 PM, Damm, Edward F. (E. Buddy) wrote: Dan, is the output below normal when using --inline Yes, the --inline flag always throws up a whole slew of compiler junk output and we haven't figured how to turn it off. It is nothing to worry about, however. , or is this an indication that the installation is not right and that I need to make a change somewhere? No, just compiler information being spewed. Baseline FiPy 1.0 is 3:35 mins installing and running FiPy 1.1 gets me down to 3:15 Changing a time stepping value in my input brings it down to 2:45 running with --inline goes down to 2:25 but.... Times for short simulations are a little misleading because there is a disproportionate time spent setting up that is only a one time cost. It is better just to get a number per time step, this is a more useful comparison.  when I run inline I get all this output shown below.  I assumed that It just needed to install the first time, so I ran it again but got a similar thing.  It seemed that it took about 10-15 SEC to run through all the compiling the second time, which may mean that solution run time was more like 2:10-2:15 minutes, but I can't say for sure when the compiling was done, and when the problem solution began.  Also, when I run with the --inline flag, only one of my 2 plots updates.  Sometimes the conserved field plot, sometimes the non-conserved. Not sure what is happening or why the --inline flag would cause this problem necessarily. Try playing with the number of viewers and the variables being plotted. Also, try and turn off as much of the other stuff as possible and see what happens. Daniel Wheeler