Hello Hui --

Generally CHPL_TASKS=qthreads outperforms CHPL_TASKS=fifo at all but the 
smallest scales.  We would need to know a lot more to come to any worthwhile 
conclusions.  What is the output of `printchplenv --anonymize` for your 
configurations (I assume they differ only in terms of the CHPL_TASKS setting)?  
Are you using any compilation options other than ‘--fast’?  What execution 
options are you using?  Are you setting any execution-time environment 
variables (CHPL_RT_*) and if so, to what values?   And finally, what is the 
target architecture (number of nodes, number of CPU cores per node, etc.)?

thanks,
greg


> On Aug 15, 2017, at 9:59 AM, Hui Zhang <[email protected]> wrote:
> 
> Hello,
> 
> I did some performance comparison between qthreads and fifo with 3 
> benchmakrs: lulesh, hpl, and isx. I expected qthreads to outperform fifo in 
> all cases, but the result turns out to be superising. 
> For lulesh and hpl, in all tests (#nodes from 2 to 32), qthreads is much 
> slower (took 1.5~10x longer than that of fifo). For isx, qthreads beats fifo 
> with speedup of 1.5~2x.
> 
> All benchmarks compiled with --fast and I'm using 1.15. So is what I'm 
> getting here reasonable? Any previous performance comparison between fifo and 
> qthreads on those benchmarks?
> 
> Thanks
> 
> -- 
> Best regards
> 
> 
> Hui Zhang
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot_______________________________________________
> Chapel-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/chapel-developers

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers

Reply via email to