Skip to content

Commit

Permalink
deploy: 7dcc9bd
Browse files Browse the repository at this point in the history
  • Loading branch information
hagau committed May 28, 2024
1 parent 2d8170f commit 9525c45
Show file tree
Hide file tree
Showing 5 changed files with 13 additions and 5 deletions.
Binary file modified .doctrees/cluster_managment.doctree
Binary file not shown.
Binary file modified .doctrees/environment.pickle
Binary file not shown.
8 changes: 6 additions & 2 deletions _sources/cluster_managment.md.txt
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,12 @@ for details on configuring the numexpr threadpool.
Note that not every operation can be parallelized (and I/O speed can sometimes
limit performance as well), therefore the actual performance is often more
limited by the framework code and the code in the recipe than by the available
cores. To achieve (near) optimal performance, some experimentation with the
actual workload is most likely necessary.
cores. Note also that the dask documentation suggests setting the number of numexpr
threads to one (see [here](https://github.com/dask/dask/discussions/8098) and
[here](https://docs.dask.org/en/latest/generated/dask.dataframe.DataFrame.query.html)).
This might not be the most optimal suggestion for every workload, so to achieve
more optimal performance, some experimentation with the actual workload is most
likely necessary.

If you are using a SLURM node on a partition other than the default (check with
`sinfo -Nl`), add `--partition <partition_name>` to the call.
Expand Down
8 changes: 6 additions & 2 deletions cluster_managment.html
Original file line number Diff line number Diff line change
Expand Up @@ -114,8 +114,12 @@ <h1>Running on a cluster<a class="headerlink" href="#running-on-a-cluster" title
Note that not every operation can be parallelized (and I/O speed can sometimes
limit performance as well), therefore the actual performance is often more
limited by the framework code and the code in the recipe than by the available
cores. To achieve (near) optimal performance, some experimentation with the
actual workload is most likely necessary.</p>
cores. Note also that the dask documentation suggests setting the number of numexpr
threads to one (see <a class="reference external" href="https://github.com/dask/dask/discussions/8098">here</a> and
<a class="reference external" href="https://docs.dask.org/en/latest/generated/dask.dataframe.DataFrame.query.html">here</a>).
This might not be the most optimal suggestion for every workload, so to achieve
more optimal performance, some experimentation with the actual workload is most
likely necessary.</p>
<p>If you are using a SLURM node on a partition other than the default (check with
<code class="docutils literal notranslate"><span class="pre">sinfo</span> <span class="pre">-Nl</span></code>), add <code class="docutils literal notranslate"><span class="pre">--partition</span> <span class="pre">&lt;partition_name&gt;</span></code> to the call.</p>
<p>A already running dask cluster can be used by appending <code class="docutils literal notranslate"><span class="pre">--cluster</span> <span class="pre">&lt;cluster_address&gt;</span></code> to the command line. See the setup
Expand Down
2 changes: 1 addition & 1 deletion searchindex.js

Large diffs are not rendered by default.

0 comments on commit 9525c45

Please sign in to comment.