Objet : Developers list for StarPU
Archives de la liste
- From: Samuel Thibault <samuel.thibault@ens-lyon.org>
- To: Miguel Palhas <mpalhas@gmail.com>
- Cc: starpu-devel@lists.gforge.inria.fr
- Subject: Re: [Starpu-devel] Problems using parallel tasks
- Date: Wed, 5 Jun 2013 13:29:09 +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>
Miguel Palhas, le Wed 05 Jun 2013 12:24:36 +0100, a écrit :
> I hadn't read that part yet, but i was indeed trying to run this code with:
>
> STARPU_SCHED=pheft ./a.out
>
> And i would expect it to try to run the task first with 1 thread, and scale
> in
> future invocations. So i would expect that multiple invocation of the call()
> function in my example would try to use different worker sizes right?
Yes, but StarPU does not rely on just one task duration measurement, it
waits for _STARPU_CALIBRATION_MINIMUM 10 measurements.
> After reading that paragraph, i tried to use the peager scheduler as
> mentioned,
> but it doesn't seem to exist. I have however a pgreedy one,
> Is pgreedy and peager the same i supose?
It was renamed into peager later on yes.
Samuel
- [Starpu-devel] Problems using parallel tasks, Miguel Palhas, 05/06/2013
- Re: [Starpu-devel] Problems using parallel tasks, Samuel Thibault, 05/06/2013
- Re: [Starpu-devel] Problems using parallel tasks, Miguel Palhas, 05/06/2013
- Re: [Starpu-devel] Problems using parallel tasks, Samuel Thibault, 05/06/2013
- Re: [Starpu-devel] Problems using parallel tasks, Miguel Palhas, 05/06/2013
- Re: [Starpu-devel] Problems using parallel tasks, Samuel Thibault, 05/06/2013
Archives gérées par MHonArc 2.6.19+.