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

[Samuel Thibault <samuel.thibault@inria.fr>]

Hello,

Which version of StarPU is this?

Which scheduler did you use? The default scheduler in StarPU 1.2 is
still "eager", which is a real bottleneck for 60-y-core systems :)

Using "lws" would probably be a better go.

Trying the StarPU trunk (it is very stable ATM, we will probably branch
to 1.3 sooner or later) could be useful too, its default scheduler is
now lws too.

Also, you might want to try the trunk's --enable-numa option. It is
still very experimental and was not really benchmarked, but possibly it
could help.

Are there priorities defined in your algorithm?

Samuel