diff --git a/docs/farming-&-staking/farming/additional-guides/gpu-plotter.mdx b/docs/farming-&-staking/farming/additional-guides/gpu-plotter.mdx index 5a52367f560..029b9561dac 100644 --- a/docs/farming-&-staking/farming/additional-guides/gpu-plotter.mdx +++ b/docs/farming-&-staking/farming/additional-guides/gpu-plotter.mdx @@ -36,161 +36,4 @@ GPU plotting employs the new v1 plot format, which is applicable to any plots cr 🛠️ Limited AMD support is available in recent test builds. The most recent test builds are linked on the [forum](https://forum.autonomys.xyz/t/rocm-gpu-support-amd/4440). See Discord [farmer-chat](https://discord.com/channels/864285291518361610/1062507270539321485) channel for limited support. - - - -## Supported GPUs - - - - - - -| Series & Model | Supported | -|---|:--:| -| RTX 20xx and Newer | ✅ | -| GTX 16 Series | ✅ | - -
- *Nvidia [drivers](https://developer.nvidia.com/cuda-downloads) version 550 or later are required. Installing the CUDA Toolkit is not required.* -
- - - - - -:::tip Latest Test Build - -You must be using the latest test build for AMD support. - -::: - -| Series & Model | Ubuntu | Windows | -|---|:---:|:---:| -| RX 7900 XTX | ✅ | ❔ | -| RX 7600 XT | ✅ | ❔ | -| RX 7600 | ✅ | ❔ | -| RX 6800 | ✅ | ❔ | -| RX 6600 | ✅ | ❔ | -| RX 5700 XT | ❌ | ❔ | -| RX 5700 | ❌ | ❔ | -| RX 5600 | ❌ | ❔ | -| AMD BC-250 | ❌ | ❔ | - - - - - -Intel Arc GPUs *may* be supported in the future, but specific compatibility details have not been announced yet. - - - - - -### AMD ROCm support - -:::caution AMD ROCm Support - -*There are many challenges to overcome regarding AMD ROCm support. There is much more information on this topic on the [forum](https://forum.autonomys.xyz/t/rocm-gpu-support-amd/4440).* - -::: - - - - - -:::tip Using ROCm with Subspace Farmer - -The `subspace-farmer-rocm-*` binaries provide ROCm support, with corresponding CLI options similar to CUDA and prefixed with `--rocm`. - -::: - -1. In order to install necessary libraries go to Ubuntu native installation — [ROCm installation (Linux)](https://rocm.docs.amd.com/projects/install-on-linux/en/docs-6.2.2/install/native-install/ubuntu.html) and follow these steps for your Ubuntu version: - - - Package signing key - - Register ROCm packages - -You don't need a custom driver or full ROCm toolchain to use already compiled application, so skip all other steps. - -2. Next install a single package with ROCm runtime: - - ```bash - sudo apt-get install --no-install-recommends hip-runtime-amd - ``` - -And register the library so that farmer and other apps can find it: - - ```bash - echo "/opt/rocm/lib" | sudo tee /etc/ld.so.conf.d/rocm.conf > /dev/null - sudo ldconfig - ``` - -3. Then, to allow the user to access GPU for compute purposes, you need to add your user to render group (please never run farmer as root with sudo :pray:): - - ```bash - sudo usermod -a -G render $LOGNAME - ``` - -4. Now you'll need to log out of your user profile and log back in or simply reboot for group changes to take effect and you're ready to go. - - - - - -:::tip Using ROCm with Subspace Farmer - -The `subspace-farmer-rocm-*` executables provide ROCm support, with corresponding CLI options similar to CUDA and prefixed with `--rocm`. - -::: - -In order to install necessary libraries go to [https://www.amd.com/en/developer/resources/rocm-hub/hip-sdk.html](https://www.amd.com/en/developer/resources/rocm-hub/hip-sdk.html) and download ROCm version 6.1.2 for your Windows version. - -In the installer just the HIP RTC Runtime should be enough under “HIP Runtime Compiler → HIP RTC Runtime 6.1.0”, everything else can be unchecked. - - - - - -:::note Simplified Cross-Compilation - -- Cross-compilation no longer requires separate Dockerfiles (which is why they are removed), both native and cross-compilation is supported with a single file -- Container image is now built as multi-platform, meaning no -aarch64 suffix and no awkwardness related to that -- Aarch64 farmer container image is now compiled with CUDA support (while regular executable isn't) - -::: - -Container image now ships with a second executable `/subspace-farmer-rocm` (see explanation above as to why second binary is needed). - -Here is how it can be used with Docker Compose, you can use this as an inspiration for other use cases: - -```text -services: - famer: - image: ghcr.io/autonomys/farmer:TAG - # Beginning of ROCm-specific options - devices: - - /dev/kfd:/dev/kfd - # This will make all GPUs accessible, you can also limit this - # to individual devices like `/dev/dri/renderD128` - - /dev/dri:/dev/dri - security_opt: - - seccomp:unconfined - # `root` user can be replaced with ID of the user on the host system - # that is in `render` group, needed to access `/dev/kfd` device - user: root - entrypoint: /subspace-farmer-rocm - # End of ROCm-specific options - ...the rest of typical options you'd normally use -``` - - - - -## 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. - - -## Known Issues - -- Many times you will not use all of the compute power of your GPU. While this will be addressed in the future, a workaround when running a farming cluster is to run multiple instances of the plotter on the same machine. \ No newline at end of file + \ No newline at end of file