Objet : Developers list for StarPU
Archives de la liste
- From: Usman Dastgeer <usman.dastgeer@liu.se>
- To: "<starpu-devel@lists.gforge.inria.fr>" <starpu-devel@lists.gforge.inria.fr>
- Subject: [Starpu-devel] heft scheduler with can_execute hook
- Date: Mon, 15 Oct 2012 13:12:05 +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>
I made a test program with 4 cpu and 8 cuda implementations. I tried heft scheduler and noticed some weird behaviours.
On CPU when using multiple implementations: The scheduler does not try/use all workers. It just tries all implementations on worker 0? and select best to continue next executions. The other CPU workers are not used at all. I know that the tasks have dependencies but still at least when no information is available it should try different workers besides different implementations as it do for multiple cuda workers where it tries both?
--
Usman.
- [Starpu-devel] heft scheduler with can_execute hook, Usman Dastgeer, 15/10/2012
- Re: [Starpu-devel] heft scheduler with can_execute hook, Samuel Thibault, 15/10/2012
Archives gérées par MHonArc 2.6.19+.