[petsc-users] An issue about pipelined CG and Gropp's CG

赵刚 zhaog6 at lsec.cc.ac.cn
Wed Feb 17 20:31:14 CST 2021


Dear Barry,

Thank you for your prompt reply. I run ~16M DOFs on 32 nodes (36 cores per node), but CG seems to be faster than pipelined CG and Gropp's CG, I'm puzzled and haven't figured out why. Put the performance output into attachment, please check it.



Thanks,
Gang


> -----原始邮件-----
> 发件人: "Barry Smith" <bsmith at petsc.dev>
> 发送时间: 2021-02-18 09:17:17 (星期四)
> 收件人: "赵刚" <zhaog6 at lsec.cc.ac.cn>
> 抄送: PETSc <petsc-users at mcs.anl.gov>
> 主题: Re: [petsc-users] An issue about pipelined CG and Gropp's CG
> 
> 
> 
> > On Feb 17, 2021, at 6:47 PM, 赵刚 <zhaog6 at lsec.cc.ac.cn> wrote:
> > 
> > Dear PETSc team,
> > 
> > I am interested in pipelined CG (-ksp_type pipecg) and Gropp's CG (-ksp_type groppcg), it is expected that this iterative method with pipelined has advantages over traditional CG in the case of multiple processes. So I'd like to ask for Poisson problem, how many computing nodes do I need to show the advantages of pipelined CG or Gropp's CG over CG (No preconditioner is used)?
> > 
> > Currently, I can only use up to 32 nodes (36 cores per nodes) at most on my cluster, but both "pipecg" and "groppcg" seem to be no advantage over "cg" when I solve Poisson equations with homogeneous Dirichlet BC in [0, 1]^2 (remain 20K~60K DOFs per process). I guess the reason would be too few computing nodes.
> 
>   900 cores (assuming they are not memory bandwidth bound) might be enough to see some differences but the differences are likely so small compared to other parallel issues that affect performance that you see no consistently measurable difference.
> 
>    Run with -log_view three cases, no pipeline and the two pipelines and send the output. By studying where the time is spent in the different regions of the code with this output one may be able to say something about the pipeline affect.
> 
>   Barry
> 
> 
> > 
> > Because I am calling PETSc via other numerical software, if need, I would mail related performance information to you by using command line options suggested by PETSc. Thank you.
> > 
> > 
> > Thanks,
> > Gang
</zhaog6 at lsec.cc.ac.cn></petsc-users at mcs.anl.gov></zhaog6 at lsec.cc.ac.cn></bsmith at petsc.dev>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cg.out
Type: application/octet-stream
Size: 14940 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20210218/ff3dc643/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: groppcg.out
Type: application/octet-stream
Size: 15189 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20210218/ff3dc643/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pipecg.out
Type: application/octet-stream
Size: 15063 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20210218/ff3dc643/attachment-0005.obj>


More information about the petsc-users mailing list