En particular, cuando corras en **Kubernetes** probablemente **no** querrás usar workers y en cambio correr **un solo proceso de Uvicorn por contenedor**, pero te contaré sobre eso más adelante en ese capítulo.

///

## Múltiples Workers { #multiple-workers }

Puedes iniciar múltiples workers con la opción de línea de comando `--workers`:

//// tab | `fastapi`

Si usas el comando `fastapi`:

<div class="termy">

///

## Mehrere Worker { #multiple-workers }

Sie können mehrere Worker mit der `--workers`-Befehlszeilenoption starten:

//// tab | `fastapi`

Wenn Sie den `fastapi`-Befehl verwenden:

<div class="termy">

```console
$ <font color="#4E9A06">fastapi</font> run --workers 4 <u style="text-decoration-style:solid">main.py</u>

Así que, en este caso, **no** querrías tener múltiples workers en el contenedor, por ejemplo, con la opción de línea de comandos `--workers`. Querrías tener solo un **proceso Uvicorn por contenedor** (pero probablemente múltiples contenedores).

Pero en muchos casos, querrás ejecutar varios worker processes al mismo tiempo.

### Múltiples Procesos - Workers { #multiple-processes-workers }

    "path": "platforms/enterprise/enterprise-plugin-performance",
    "unitTests": false,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "enterprise-workers",
    "path": "platforms/enterprise/enterprise-workers",
    "unitTests": false,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "execution",
    "path": "platforms/core-execution/execution",

COPY ./app /code/app

# (1)!
CMD ["fastapi", "run", "app/main.py", "--port", "80", "--workers", "4"]
```

1. Hier verwenden wir die `--workers` Befehlszeilenoption, um die Anzahl der Worker auf 4 festzulegen.

Hier sind einige Beispiele, wann das sinnvoll sein könnte:

#### Eine einfache Anwendung { #a-simple-app }

    listOf(
        // We pass the 'maxParallelForks' setting as 'workers.max' to limit the maximum number of executers even
        // if multiple test tasks run in parallel. We also pass it to the Gradle build as a maximum (maxParallelForks)
        // for each test task, such that we are independent of whatever default value is defined in the build itself.
        "-Dorg.gradle.workers.max=$maxParallelForks",
        "-PmaxParallelForks=$maxParallelForks",

  "durations" : [ {
    "testProject" : "nativeMonolithic",
    "linux" : 1215
  }, {
    "testProject" : "nativeMonolithicOverlapping",
    "linux" : 1324
  } ]
}, {
  "scenario" : "org.gradle.performance.regression.nativeplatform.RealWorldNativePluginPerformanceTest.build with 12 parallel workers",
  "durations" : [ {
    "testProject" : "nativeMonolithic",

      "coverage" : {
        "per_day" : [ "linux" ]
      }
    } ]
  }, {
    "testId" : "org.gradle.performance.regression.nativeplatform.RealWorldNativePluginPerformanceTest.build with 0 parallel workers",
    "groups" : [ {
      "testProject" : "nativeMonolithic",
      "coverage" : {
        "per_commit" : [ "linux" ]
      }
    }, {
      "testProject" : "nativeMonolithicOverlapping",

            <option value="$PROJECT_DIR$/platforms/core-execution/snapshots" />
            <option value="$PROJECT_DIR$/platforms/core-execution/worker-main" />
            <option value="$PROJECT_DIR$/platforms/core-execution/workers" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/base-asm" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/base-services" />