Merge pull request #709 from autonomys/fix_gpu_plotter_page

Remove all details tags
autonomys · Oct 25, 2024 · 4327483 · 4327483
2 parents fdf1096 + 7d80e4b
commit 4327483
Showing 1 changed file with 0 additions and 37 deletions.
diff --git a/docs/farming-&-staking/farming/additional-guides/gpu-plotter.mdx b/docs/farming-&-staking/farming/additional-guides/gpu-plotter.mdx
@@ -186,43 +186,6 @@ services:
 </TabItem>
 </Tabs>
 
-## Common Plotting Parameters
-
-<details>
-<summary>Enable CPU Plotting</summary>
-
-When a compatible GPU is detected, CPU plotting is automatically disabled by default, but can be re-enabled if needed by specifying number of concurrently encoded sectors: `--cpu-sector-encoding-concurrency <sectors>`
-
-```bash
---cpu-sector-encoding-concurrency 2
-```
-
-</details>
-
-<details>
-<summary>Disable GPU Plotting</summary>
-
-```bash title="Linux"
---cuda-gpus ""
-```
-
-```powershell title="Windows"
---cuda-gpus 99
-```
-
-</details>
-
-<details>
-<summary>Specify spacific GPUs</summary>
-
-Specify particular GPUs for plotting rather than using all available GPUs (the default configuration employs all compatible GPUs): `--cuda-gpus <gpu_ids>`
-
-```bash
---cuda-gpus 0,1,3
-```
-
-</details>
-
 ## Farming Cluster
 
 When utilizing Farming Cluster, particularly with multiple or fast GPUs, you might encounter limitations due to your network's bandwidth. High performance GPUs can easily surpass the capacity of a 1G connection. While this won't cause the process to fail, it may result in your GPU idling as it waits for data to transfer. To optimize performance in such scenarios, consider upgrading to networking solutions of 2.5G, 10G, or higher.