ClearML/clearml-agent
1
0
Fork 0
mirror of https://github.com/clearml/clearml-agent synced 2025-02-12 07:38:04 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Allegro AI 2019-10-30 13:15:32 +02:00 committed by GitHub
parent d7841036d7
commit 25e49df121
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
README.md
View File

@ -180,10 +180,10 @@ NVIDIA_VISIBLE_DEVICES=0 trains-agent daemon --queue default &
NVIDIA_VISIBLE_DEVICES=1 trains-agent daemon --queue default & NVIDIA_VISIBLE_DEVICES=1 trains-agent daemon --queue default &
``` ```
Example: spin two agents, with two gpu's per agent: Example: spin two agents, pulling from dedicated `dual_gpu` queue, two gpu's per agent
```bash ```bash
NVIDIA_VISIBLE_DEVICES=0,1 trains-agent daemon --queue default & NVIDIA_VISIBLE_DEVICES=0,1 trains-agent daemon --queue dual_gpu &
NVIDIA_VISIBLE_DEVICES=2,3 trains-agent daemon --queue default & NVIDIA_VISIBLE_DEVICES=2,3 trains-agent daemon --queue dual_gpu &
``` ```
#### Starting the TRAINS Agent in docker mode #### Starting the TRAINS Agent in docker mode
@ -198,16 +198,16 @@ For actual service mode, all the stdout will be stored automatically into a file
trains-agent daemon --queue default --docker trains-agent daemon --queue default --docker
``` ```
Example: spin two agents, one per gpu on the same machine: Example: spin two agents, one per gpu on the same machine, with default nvidia/cuda docker:
```bash ```bash
NVIDIA_VISIBLE_DEVICES=0 trains-agent daemon --queue default --docker & NVIDIA_VISIBLE_DEVICES=0 trains-agent daemon --queue default --docker nvidia/cuda &
NVIDIA_VISIBLE_DEVICES=1 trains-agent daemon --queue default --docker & NVIDIA_VISIBLE_DEVICES=1 trains-agent daemon --queue default --docker nvidia/cuda &
``` ```
Example: spin two agents, with two gpu's per agent: Example: spin two agents, pulling from dedicated `dual_gpu` queue, two gpu's per agent, with default nvidia/cuda docker:
```bash ```bash
NVIDIA_VISIBLE_DEVICES=0,1 trains-agent daemon --queue default --docker & NVIDIA_VISIBLE_DEVICES=0,1 trains-agent daemon --queue dual_gpu --docker nvidia/cuda &
NVIDIA_VISIBLE_DEVICES=2,3 trains-agent daemon --queue default --docker & NVIDIA_VISIBLE_DEVICES=2,3 trains-agent daemon --queue dual_gpu --docker nvidia/cuda &
``` ```
#### Starting the TRAINS Agent - Priority Queues #### Starting the TRAINS Agent - Priority Queues
@ -220,7 +220,9 @@ trains-agent daemon --queue important_jobs default
``` ```
The **TRAINS agent** will first try to pull jobs from the `important_jobs` queue, only then it will fetch a job from the `default` queue. The **TRAINS agent** will first try to pull jobs from the `important_jobs` queue, only then it will fetch a job from the `default` queue.
# How do I create an experiment on the TRAINS server? <a name="from-scratch"></a> Adding queues, managing job order within a queue and moving jobs between queues, is available using the Web UI, see example on our [open server](https://demoapp.trains.allegro.ai/workers-and-queues/queues)
# How do I create an experiment on the TRAINS server? <a name="from-scratch"></a>
* Integrate [TRAINS](https://github.com/allegroai/trains) with your code * Integrate [TRAINS](https://github.com/allegroai/trains) with your code
* Execute the code on your machine (Manually / PyCharm / Jupyter Notebook) * Execute the code on your machine (Manually / PyCharm / Jupyter Notebook)
* As your code is running, **TRAINS** creates an experiment logging all the necessary execution information: * As your code is running, **TRAINS** creates an experiment logging all the necessary execution information: