|
|
@@ -1242,7 +1242,7 @@ it as an estimation. History is done per task size, by using a hash of the input
|
|
|
and ouput sizes as an index.
|
|
|
It will also save it in @code{~/.starpu/sampling/codelets}
|
|
|
for further executions, and can be observed by using the
|
|
|
-@code{starpu_perfmodel_display} command. The following is a small code example.
|
|
|
+@code{starpu_perfmodel_display} command. The models are indexed by machine name. To share the models between machines (e.g. for a homogeneous cluster), use @code{export STARPU_HOSTNAME=some_global_name}. The following is a small code example.
|
|
|
|
|
|
@cartouche
|
|
|
@smallexample
|
|
|
@@ -1584,7 +1584,9 @@ of processing unit. For this to be possible, the application programmer needs
|
|
|
to configure a performance model for the codelets of the application (see
|
|
|
@ref{Performance model example} for instance). History-based performance models
|
|
|
use on-line calibration. StarPU will automatically calibrate codelets
|
|
|
-which have never been calibrated yet. To force continuing calibration, use
|
|
|
+which have never been calibrated yet, and save the result in
|
|
|
+@code{~/.starpu/sampling/codelets}.
|
|
|
+The models are indexed by machine name. To share the models between machines (e.g. for a homogeneous cluster), use @code{export STARPU_HOSTNAME=some_global_name}. To force continuing calibration, use
|
|
|
@code{export STARPU_CALIBRATE=1} . This may be necessary if your application
|
|
|
has not-so-stable performance. Details on the current performance model status
|
|
|
can be obtained from the @code{starpu_perfmodel_display} command: the @code{-l}
|
