I did provide the execution times in my first email. I have copied it once more for quick reference,

no parallelization                                                 :  7 hrs and 58 mins
-parallel                       (coarse parallelization)    :  4 hrs and 39 mins
-parallel -openmp 8     (fine parallelization)         :  4 hrs and 34 mins
-parallel -openmp 14   (fine parallelization )        :  4 hrs and 37 mins


I have attached the logs to this email. The naming convention is as follows,

serial_recon-all.log           :   serial execution with no parallelization
parallel_recon-all.log        :   parallelization using -parallel
openmp8_recon-all.log     :   parallelization using -parallel -openmp 8
openmp14_recon-all.log   :   parallelization using -parallel -openmp 14

I'll rerun this with -time later and see what I get. It is gonna take some time to get those logs.

Thanks,
Tyson

On Mon, Feb 13, 2017 at 3:19 PM, Douglas N Greve <greve@nmr.mgh.harvard.edu> wrote:
What are your execution times? Can you send the recon-all files for your
parallel and non-parallel runs? If you run it with -time, then lots of
information will be printed to the log for each command. This can be
helpful for debugging these types of things.


On 02/13/2017 05:13 PM, Francis Tyson Thomas wrote:
> Hi,
>
> I have run recon-all with both -parallel enabled (including different
> openmp threads) and disabled and I'm not able to get processing times
> same as the information provided in recon-all help. The CPU used is
> *Dual Intel **Xeon E5-2623 v3* paired with 32GB DDR4 RAM. Is the
> configuration presented in recon-all help a dual cpu configuration?
>
> Following are the runtimes I have obtained,
>
> no parallelization                               :  7 hrs and 58 mins
> -parallel (coarse parallelization)                  :  4 hrs and 39 mins
> -parallel (fine parallelization; -openmp 8)    :  4 hrs and 34 mins
> -parallel (fine parallelization; -openmp 14)  :  4 hrs and 37 mins
>
> Somehow varying the number of threads is having no effect in the
> execution time of recon-all as can been seen from the processing
> times. If you can explain what could be possibly going wrong here, it
> will help me in speeding it up further.
>
> Thanks,
> Tyson
>
>
> _______________________________________________
> Freesurfer mailing list
> Freesurfer@nmr.mgh.harvard.edu
> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer

--
Douglas N. Greve, Ph.D.
MGH-NMR Center
greve@nmr.mgh.harvard.edu
Phone Number: 617-724-2358
Fax: 617-726-7422

Bugs: surfer.nmr.mgh.harvard.edu/fswiki/BugReporting
FileDrop: https://gate.nmr.mgh.harvard.edu/filedrop2
www.nmr.mgh.harvard.edu/facility/filedrop/index.html
Outgoing: ftp://surfer.nmr.mgh.harvard.edu/transfer/outgoing/flat/greve/

_______________________________________________
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.