Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Performance profiling of tile low rank cholesky (HiCMA) with StarPU on distributed memory systems

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Performance profiling of tile low rank cholesky (HiCMA) with StarPU on distributed memory systems


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@inria.fr>
  • To: Aniello Esposito <esposito@cray.com>
  • Cc: Kadir Akbudak <kadir.akbudak@kaust.edu.sa>, "starpu-devel@lists.gforge.inria.fr" <starpu-devel@lists.gforge.inria.fr>, Hatem Ltaief <hatem.ltaief@kaust.edu.sa>, "Sameh M. Abdulah" <sameh.abdulah@kaust.edu.sa>, Aleksandr Mikhalev <aleksandr.mikhalev@kaust.edu.sa>
  • Subject: Re: [Starpu-devel] Performance profiling of tile low rank cholesky (HiCMA) with StarPU on distributed memory systems
  • Date: Wed, 2 May 2018 19:30:13 +0200
  • Authentication-results: mail2-smtp-roc.national.inria.fr; spf=None smtp.pra=samuel.thibault@inria.fr; spf=Neutral smtp.mailfrom=samuel.thibault@ens-lyon.org; spf=Pass smtp.helo=postmaster@hera.aquilenet.fr
  • Ironport-phdr: 9a23:wIa7KhOwqZrYzJcFZBYl6mtUPXoX/o7sNwtQ0KIMzox0Iv/9rarrMEGX3/hxlliBBdydt6ofzbKO+4nbGkU4qa6bt34DdJEeHzQksu4x2zIaPcieFEfgJ+TrZSFpVO5LVVti4m3peRMNQJW2aFLduGC94iAPERvjKwV1Ov71GonPhMiryuy+4ZLebxlGiTanfb9+MAi9oBnMuMURnYZsMLs6xAHTontPdeRWxGdoKkyWkh3h+Mq+/4Nt/jpJtf45+MFOTav1f6IjTbxFFzsmKHw65NfqtRbYUwSC4GYXX3gMnRpJBwjF6wz6Xov0vyDnuOdxxDWWMMvrRr0vRz+s87lkRwPpiCcfNj427mfXitBrjKlGpB6tvgFzz5LIbI2QMvd1Y6HTcs4ARWdZUMhfVzJPDJ6/YYsBAOUOIftXoIv6p1QAtha+GRWgCP/zxjNUnHL6w6s32PkhHwHc2wwgGsoDvmnOo9XwKacdT+S1x7TWwzXDbvNZwi3y6JXMchA9vPqBWqlwftDUyUkyCQzFik+cqZDlPzOUzesCqXWb7+58Ve+0im4nrRtxojm1ycs2hInJnJsYx1bZ/it62IY4PcC0RU17bNK+DpdduS+XO5FrTs8+X21kojs2xqUbtZO5fSUG0okryh7cZvCdboSE/w/vWPyMLTtmgn9uZaixiAyo8Ue6z+3xTsm030hOripCitTMtm4C1wbJ5cSdUPR951qh2TeL1w/N7OFLP1w0mbDVK5472rIwl5wTvlrfHiLuhUn7j6+bel869uWm5enreKjqqoOAO4Nulw3yKqEulda+AeQ8PAgORW+b+eGk2b3450L5RahKgeMykqXDrJDaJcUbqbWjDA9I1oYj9w2yACmg0NQDhHUHKFJEeBWBj4TzPFHOOv/4Ae+lg1uwiDdr2+zGPrr5D5XWMnjMiq3hfa5g60JF1QU8085f6IxQCrwaJPLzW1TxtMDDDhMjPAy0zeHnCM9y1owAQ26PA6mZMLnTsVCS/O4vLfOMN8cpv2PULfko4/rpxVIigVgGfLWulc8ac2i/BfV6JG2Se3P9xNwGFDFZkBA5SbnRgVifXDobW3azVash4i1zXJmvCJrOQsaxgL2L1Tq/ArVXYHpHAxaCCyG7JM2/R/4QZXfKcYdamTseWO3kEtd5jED8hErB07Nia9Hs1GgdvJPn2sJy4rSPxxw07nlwHsOblWaXQDMuxz9ad3oNxKl65HdF5BKby6Eh265ZE8ZS7rVHSFVibMOO/6lBE9n3Hzn5UJKJRVKhG4T0ATwrR5Q42sIPZ0t7FsnkgAqRhic=
  • 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

Aniello Esposito, le mer. 02 mai 2018 17:08:48 +0000, a ecrit:
> As Hatem already emphasized, the main point here is the behavior of threads
> in the presence of not enough work. We would have expected no real
> difference if even
> too many threads are used.

Sure, but that's precisely where a centralized scheduler like prio would
suffer from all the idle threads trying to pick up work from the central
place, tasks getting executed randomly on various CPUs, etc.

Samuel




Archives gérées par MHonArc 2.6.19+.

Haut de le page