|
|
@@ -317,7 +317,8 @@ 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, or drawn by using
|
|
|
-the @code{starpu_perfmodel_plot}. The models are indexed by machine name. To
|
|
|
+the @code{starpu_perfmodel_plot} (@pxref{Performance model calibration}). 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}. Measurements are only done when using a task scheduler which makes use of it, such as @code{heft} or @code{dmda}.
|
|
|
|
|
|
@@ -366,7 +367,7 @@ and maximum observed input size. It can be useful to set the
|
|
|
@code{STARPU_CALIBRATE} environment variable to @code{1} and run the application
|
|
|
on varying input sizes, so as to feed the performance model for a variety of
|
|
|
inputs. The @code{starpu_perfmodel_display} and @code{starpu_perfmodel_plot}
|
|
|
-tools can be used to observe how much the performance model is calibrated; when
|
|
|
+tools can be used to observe how much the performance model is calibrated (@pxref{Performance model calibration}); when
|
|
|
their output look good, @code{STARPU_CALIBRATE} can be reset to @code{0} to let
|
|
|
StarPU use the resulting performance model without recording new measures. If
|
|
|
the data input sizes vary a lot, it is really important to set
|
