running time

[mohammad safarzadeh]

I am running a test run , and I see that a day it takes 32 hours to finish the run and in another day 48 hours is not enough!

I contacted the people on the machine which is shared memory

http://www.princeton.edu/researchcomputing/computational-hardware/machine-3/

 and they told me that you are I/O bound and asked me these question:

If you are I/O bound, are you doing your I/O in large chunks?

Have you profiled you code to figure out where it might be spending all 
the time?

How much data does your job read?  How much does it write?  When does
it do either (all at the beginning and end, or throughout execution)?
These kinds of things can affect start time, end time, and general
execution time.

[Chris Hayward]

Hi Mohammad,

Typically, my runs are not I/O-bound, so I am surprised to hear this. However, as explained previously, it is very difficult to comment on such issues without seeing your parameter files and outputs and knowing details about the input simulations. Furthermore, we cannot do profiling for you. I suggest that you perform this with a collaborator who is familiar with profiling code.

Cheers,

Chris

--
You received this message because you are subscribed to the Google Groups "Sunrise" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sunrisemcrx...@googlegroups.com.
To post to this group, send email to sunri...@googlegroups.com.
Visit this group at http://groups.google.com/group/sunrisemcrx?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Chris Hayward
Heidelberger Institut für Theoretische Studien
Schloss-Wolfsbrunnenweg 35
69118 Heidelberg, Germany
Google Voice: +1 (617) 744-9416
Office: +49 6221 533 284
Fax: +49 6221 533 298
http://www.cfa.harvard.edu/~chayward