docs: refactor settings accelerator guide

docs/.vitepress/en.ts

@@ -409,20 +409,9 @@ const side = {
                 },
               ],
             },
-            { 
-              text: "Manage GPU", 
-              collapsed: true,
+            {
+              text: "Manage accelerator resources",
               link: "/manual/olares/settings/gpu-resource",
-              items:[
-                {
-                  text: "Manage single-GPU resources",
-                  link: "/manual/olares/settings/single-gpu" 
-                },
-                {
-                  text: "Manage multi-GPU resources",
-                  link: "/manual/olares/settings/multi-gpu"
-                },
-              ]
             },
             { text: "Set video playback", link: "/manual/olares/settings/video" },
             { text: "Manage search rules", link: "/manual/olares/settings/search" },

docs/.vitepress/one.en.ts

@@ -53,7 +53,7 @@ export const oneSidebar: DefaultTheme.Sidebar = {
           link: "/one/comfyui",
         },
         {
-          text: "Switch GPU mode",
+          text: "Manage accelerator resources",
           link: "/one/gpu",
         },
       ]
@@ -196,7 +196,7 @@ export const oneSidebar: DefaultTheme.Sidebar = {
           // items:
           //   [
           //     {
-          //       text: "Manage GPU",
+          //       text: "Manage accelerator resources",
           //       link: "/one/two-one-gpu",
           //     },
           //     {

docs/.vitepress/one.zh.ts

@@ -53,7 +53,7 @@ export const oneSidebar: DefaultTheme.Sidebar = {
           link: "/zh/one/comfyui",
         },
         {
-          text: "Switch GPU mode",
+          text: "Manage accelerator resources",
           link: "/zh/one/gpu",
         },
       ]
@@ -197,7 +197,7 @@ export const oneSidebar: DefaultTheme.Sidebar = {
           // items:
           //   [
           //     {
-          //       text: "Manage GPU",
+          //       text: "Manage accelerator resources",
           //       link: "/zh/one/two-one-gpu",
           //     },
           //     {

docs/.vitepress/zh.ts

@@ -405,19 +405,8 @@ const side = {
               ],
             },
             {
-              text: "管理 GPU",
-              collapsed: true,
+              text: "管理 AI 算力",
               link: "/zh/manual/olares/settings/gpu-resource",
-              items: [
-                {
-                  text: "管理单 GPU 资源",
-                  link: "/zh/manual/olares/settings/single-gpu",
-                },
-                {
-                  text: "管理多 GPU 资源",
-                  link: "/zh/manual/olares/settings/multi-gpu",
-                },
-              ],
             },
             { text: "视频设置", link: "/zh/manual/olares/settings/video" },
             { text: "文件搜索", link: "/zh/manual/olares/settings/search" },

docs/manual/olares/settings/gpu-resource.md

@@ -1,61 +1,142 @@
 ---
 outline: [2,3]
-description: Learn how GPU allocation works in Olares, including binding and unbinding, how app state affects GPU actions, and how time slicing, memory slicing, and app exclusive differ from one another.
+description: Manage accelerator resources in Olares, including GPU modes, app GPU requirements, app resume, and resource release.
 ---
-# Understand GPU management
+# Manage accelerator resources
+
+Olares uses accelerator resources to run workloads such as AI inference, image and video generation, transcoding, and gaming. An accelerator can be a GPU, an integrated accelerator chip, or a CPU-based fallback resource.
+
+This guide helps you understand how Olares allocates accelerator resources, then walks through common tasks such as changing a GPU mode, resuming a stopped app with GPU resources, and removing an app from a GPU.
+
+## Understand accelerator resources
+
+### How allocation works
+
+Olares treats GPUs and other acceleration devices as shared resources in the cluster. Instead of asking each app to manage hardware directly, Olares checks the app's accelerator requirement, finds matching resources, and binds the app to a resource that has enough available capacity.
+
+For GPU-dependent apps, Olares considers several factors during allocation:
+
+- Resource type, such as **NVIDIA GPU**.
+- GPU mode, such as **Time slicing**, **Memory slicing**, or **Exclusive**.
+- Total and free VRAM.
+- Whether the app can bind to one GPU or multiple GPUs.
+- Apps already assigned to the same resource.
+
+When you install a new app that requires GPU resources, Olares automatically binds it to a suitable GPU if enough matching capacity is available. If the app is stopped later, or if you want to choose a different GPU or mode, you can resume the app and assign resources manually.
+
+### Supported resource types
+
+Olares can display the following accelerator resource types:
+
+| Resource type | Description |
+| -- | -- |
+| **NVIDIA** | General NVIDIA GPUs. |
+| **NVIDIA GB10** | NVIDIA GB10 SoC devices. |
+| **Apple M-series** | Apple M-series chips. |
+| **AMD Strix Halo** | AMD Strix Halo devices. |
+| **CPU** | Fallback resource used when no accelerator device is available. |
 
 :::info
-Only Olares admins can change GPU modes. This helps avoid conflicts and keeps GPU performance predictable for everyone.
+AMD GPU and AMD APU devices are not covered in this version.
 :::
 
-Olares lets you manage how apps use available GPUs for workloads such as AI, image and video generation, transcoding, and gaming.
+### GPU modes
 
-In this guide, you will learn:
-- How GPU allocation works in Olares.
-- How app state affects available GPU actions.
-- How GPU modes differ and when to use each one.
+For supported GPU resources, the mode controls how apps share the GPU. Not every accelerator supports all three modes. The mode dropdown only shows the modes available for that specific resource.
 
-## How GPU allocation works
+| Mode | Description | Usage & notes |
+| -- | -- | -- |
+| **Time slicing** | Multiple apps share one GPU<br> by taking turns using compute<br> and VRAM. Each app can see <br>the full GPU, but workloads run<br> in slices. | <ul><li>**Best for**: Running several GPU-dependent apps at the same time.</li><li>**Note**: The quota for each app is fixed to the GPU's full Dedicated VRAM and cannot be edited. Launch may also be blocked by the node memory check described below.</li></ul> |
+| **Memory slicing** | Multiple apps share one GPU<br> with fixed VRAM allocations. | <ul><li>**Best for**: Running multiple GPU-dependent apps while controlling VRAM usage. </li><li>**Note**: During launch, Olares allocates the app's minimum required VRAM by default. You can adjust the allocation.</li></ul> |
+| **Exclusive** | One app gets full access to the<br> GPU. | <ul><li>**Best for**: Running heavy workloads that need maximum performance, such as large models, rendering, or high-end gaming. </li><li>**Note**: No other apps can bind to this GPU until it is released.</li></ul> |
 
-In Olares, giving an app access to GPU resources is called binding. Unbinding removes that access so the GPU can be released or reassigned.
+:::info How node memory is calculated in Time slicing
+In **Time slicing** mode, Olares currently checks node memory using these calculations:
 
-Whether you can bind or unbind an app depends mainly on whether the app is running or stopped.
+- Required memory: `App memory requirement + GPU Dedicated VRAM`
+- Memory available below the scheduling threshold: `Total node memory × 90% - Used node memory`
+- Memory shortfall: `Required memory - Available memory`
 
-| App state | Bind (Give access) | Unbind (Remove access) |
-| -- | -- | -- |
-| **Running** | Supported | Not supported. You need to stop the app first. <sup>1, 2</sup> |
-| **Stopped** | Not supported. You need to resume <br>the app first. | Supported |
+For example, suppose an app requires 20 GiB of memory and the GPU has 16 GiB of Dedicated VRAM:
+
+- Required memory: `20 GiB + 16 GiB = 36 GiB`
+- Available memory on a node with 46.89 GiB total and 7.41 GiB used: `46.89 GiB × 90% - 7.41 GiB = 34.79 GiB`
+- Memory shortfall: `36 GiB - 34.79 GiB = 1.21 GiB`
+
+Because the shortfall is greater than zero, Olares cannot schedule the app on that node.
+
+This calculation reflects the current scheduling behavior and may change as the scheduling logic is finalized.
+:::
 
-1. Stopping an app pauses its workload, but it does not automatically remove its GPU allocation. To fully release the GPU or VRAM for other workloads, you must explicitly unbind the app after stopping it.
-2. If an app is allocated to multiple GPUs on the same node, you can unbind it from one GPU while it continues running on the others.
+## View accelerator resources
 
-You can check whether an app is running or stopped in either of these places:
+Go to **Settings** > **Accelerator** to view GPU and other accelerator resources across all nodes in the cluster.
 
-- **Market** > **My Olares**: The current status is displayed on the app's card. 
-- **Settings** > **Applications**: The current status is shown in the app list. 
-- **Launchpad**: A stopped app is marked with an orange dot next to its name.
+The page shows each available resource with:
 
-## GPU modes and when to use them
+- Node name.
+- Resource type, such as **NVIDIA GPU**.
+- Dedicated VRAM on the node.
+- GPU model, such as **NVIDIA GeForce RTX 4060 Ti**.
+- Current sharing mode, such as **Time slicing**, **Memory slicing**, or **Exclusive**.
+- Apps currently assigned to the resource.
 
-Olares supports three GPU modes. Each mode determines how GPU resources are shared and what happens to running apps after you switch modes.
+![Accelerator overview](/images/manual/olares/settings-gpu-info.png#bordered)
 
-:::info DGX Spark support
-On DGX Spark, you can use **Memory slicing** and **App exclusive** to manage GPU resources.
+## Change a GPU mode
+
+:::warning
+Switching modes stops all apps currently using this GPU and removes their assigned GPU resources. To use these apps again, reassign resources and launch them.
 :::
 
-| GPU mode | How resources are<br> shared | After switching to this mode | Best for |
-| -- | -- | -- | -- |
-| **Time slicing** (Default) | Multiple apps share <br>the same GPU over <br>time. | Running apps that require a GPU are automatically assigned to share the GPU. | Running several GPU-dependent apps at the same time. |
-| **Memory slicing** | Multiple apps share <br>the GPU, with fixed <br>VRAM allocations <br>for each app. | Running apps that require a GPU are automatically added and assigned the minimum VRAM required to run. | Running multiple GPU-dependent apps while strictly controlling VRAM usage. |
-| **App exclusive** | One app gets full, <br>uninterrupted access<br> to the GPU. | One running app that requires a GPU is automatically selected and given exclusive access. | Heavy workloads that need maximum performance, such as large models, rendering, or high-end gaming. |
+1. Go to **Settings** > **Accelerator**, then click **Manage** on the resource card.
+2. On the **Manage node** page, find the target GPU, open its mode dropdown, and select **Time slicing**, **Memory slicing**, or **Exclusive**.
+
+   ![Select mode](/images/manual/olares/settings-gpu-dropdown.png#bordered)
+
+## Resume an app and assign resources
+
+You can resume a stopped app and manually assign resources from either **Settings** or **Market**.
+
+1. Open one of the following locations:
+   - **Settings** > **Applications**.
+   - **Market** > **My Olares**.
+2. Find the target app and click **Resume**.
+3. Review the app's requirements at the top of the launch dialog, including resource type, GPU binding capability, and VRAM requirement.
+4. Under **Select GPUs**, choose a resource. The dialog shows its Dedicated VRAM, sharing mode, quota for the current app, and assigned apps. If the app cannot be launched, follow the inline message:
+   - If the available quota is below the app's minimum requirement, expand **Assigned apps** and click **Remove** for an app to free resources, or select another GPU.
+   - If the GPU's total Dedicated VRAM is below the app's minimum requirement, removing apps will not help. Select another GPU.
+   - In **Time slicing** mode, launch can also be blocked by the node memory check described above. The message shows the node's total, used, and required memory. Retry later or select another node.
+
+   ![Resume an app](/images/manual/olares/settings-gpu-resume-app.png#bordered){width=70%}
+
+5. For **Memory slicing** mode, **Quota for current app** defaults to the app's minimum VRAM requirement. To adjust it, enter a new amount directly in the quota field. The value cannot exceed the available quota.
+
+   ![Set VRAM in Memory slicing mode](/images/manual/olares/settings-gpu-mem-slicing-vram.png#bordered){width=70%}
 
-:::warning App interruption notice
-Changing a GPU's mode reallocates hardware resources. Depending on the mode you choose, apps that are currently using the GPU may be paused automatically.
+   :::info Reallocate VRAM
+   You cannot adjust VRAM after the app is assigned. To change it later, you must remove the app from the GPU and resume it again.
+   :::
 
-After switching modes, check the state of your apps and manually resume them if necessary.
+6. Click **Launch**.
+
+## Remove an app from a GPU
+
+Removing an app from a GPU stops the app and releases its hardware resources. Use this workflow when you want to actively free up resources from **Settings**, even if you are not launching another app right now.
+
+To use the app again later, you must assign resources and launch it again.
+
+:::warning
+If an app is bound to multiple GPUs or GPUs across multiple nodes, removing the app from one GPU releases all GPU resources assigned to that app and stops the app.
 :::
 
-## Next steps
+1. Go to **Settings** > **Accelerator**, then click **Manage** on the resource card.
+2. Under **Assigned apps**, find the target app, then click **Remove**.
 
-- [Manage GPU resources for a single GPU](./single-gpu.md)
-- [Manage GPU resources for multiple GPUs](./multi-gpu.md)
+   ![Remove an app](/images/manual/olares/settings-gpu-remove-app.png#bordered)
+
+3. In the confirmation dialog, click **Remove**.
+
+:::info
+Resource release may take a short time. If no resource can be assigned to the app immediately after removal, refresh the resource list and check again.
+:::