From e15dde1a357923a29812728ff76107793b7c49c3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?M=C3=A1ty=C3=A1s=20Aradi?= Date: Mon, 9 Dec 2024 12:43:24 +0100 Subject: [PATCH] Fix default device selection --- docs/how-to/hip_runtime_api/multi_device.rst | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/docs/how-to/hip_runtime_api/multi_device.rst b/docs/how-to/hip_runtime_api/multi_device.rst index 3b79e37dfc..4d2fb98dcc 100644 --- a/docs/how-to/hip_runtime_api/multi_device.rst +++ b/docs/how-to/hip_runtime_api/multi_device.rst @@ -20,11 +20,7 @@ can leverage the full computational power available. Typically, applications list devices and their properties for deployment planning, and also make dynamic selections during runtime to ensure optimal performance. -If the application does not assign a specific GPU, the runtime typically -assigns one automatically based on factors such as availability, performance, -memory, and efficiency. As a result, the runtime might choose the least -utilized GPU, the one best suited for the task, the GPU with adequate memory, -or the most energy-efficient option. +If the application does not define a specific GPU, device 0 is selected. .. code-block:: cpp