Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Performance issue of StarPU on Intel self-hosted KNL

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Performance issue of StarPU on Intel self-hosted KNL


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@inria.fr>
  • To: Olivier Aumage <olivier.aumage@inria.fr>, Mawussi Zounon <mawussi.zounon@manchester.ac.uk>, Negin Bagherpour <negin.bagherpour@manchester.ac.uk>, "starpu-devel@lists.gforge.inria.fr" <starpu-devel@lists.gforge.inria.fr>, Jakub Sistek <jakub.sistek@manchester.ac.uk>
  • Subject: Re: [Starpu-devel] Performance issue of StarPU on Intel self-hosted KNL
  • Date: Mon, 25 Sep 2017 14:16:14 +0200
  • List-archive: <http://lists.gforge.inria.fr/pipermail/starpu-devel/>
  • List-id: "Developers list. For discussion of new features, code changes, etc." <starpu-devel.lists.gforge.inria.fr>
  • Organization: I am not organized

Samuel Thibault, on ven. 22 sept. 2017 11:48:12 +0200, wrote:
> Olivier Aumage, on ven. 22 sept. 2017 09:12:27 +0200, wrote:
> > The main reason for the initialization cost on KNL is the large number of
> > cores and the fact that those cores are individually much less powerful
> > and advanced than Broadwell's cores. Initializing libhwloc on the KNL
> > takes about 0.5 to 1 second.
>
> And we do it twice, once for the whole architecture, and a second
> time in _starpu_build_tree to get only the structure of the
> architecture. Perhaps that second call could be avoided, it's probably
> less expensive to make build_tree cope with structure-useless hwloc
> object, than asking hwloc discovery a second time.

I have fixed this.

Samuel




Archives gérées par MHonArc 2.6.19+.

Haut de le page