From 8cfc3679230a4f1c8b3ceeb5e643d534ea6bf1ad Mon Sep 17 00:00:00 2001 From: Malte Grosse Date: Fri, 3 May 2024 11:44:41 +0900 Subject: [PATCH] changed training --- src/sandbox/training.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/sandbox/training.md b/src/sandbox/training.md index f550240..af7927e 100644 --- a/src/sandbox/training.md +++ b/src/sandbox/training.md @@ -4,12 +4,12 @@ This documentation is for advanced users which are aware of following tools: git ## Overview Available are two worker agents with -- 12 CPUs +- 12 physical CPUs - 40 GB memory - 20 GB Nvidia GPU memory - 100 GB Hdd Diskspace -Only two pipelines can run in parallel to ensure having the promised hardware resources. If more jobs occur, they will be stored in a queue and released after the fifo principle. +Only two pipelines can run in parallel to ensure having the promised hardware resources. If more jobs occur, they will be stored in a queue and released after the fifo principle. Storage is not persistent - every build/training job needs to saved somewhere external. ## Development @@ -58,7 +58,7 @@ steps: ``` See the official [documentation](https://woodpecker-ci.org/docs/usage/workflow-syntax) for the syntax. -Generally, the pipeline is based on different steps, and in each step, another container environment can be chosen. In the example above, first an official tensorflow container with python 3 is used to run the training python script. In the second step, the model gets compressed and pushed on the temp sandbox storage. +Generally, the pipeline is based on different steps, and in each step, another container environment can be chosen. In the example above, first an official tensorflow container with python 3 is used to run the training python script. In the second step, the model gets compressed and pushed on the temp. sandbox storage. 3. Commit and push 4. See current state of the pipelines at the [overview site](https://ci.sandbox.iuk.hdm-stuttgart.de/repos)