- Sort Score
- Num 10 results
- Language All
Results 1 - 10 of 93 for worker3 (0.08 seconds)
-
docs/de/docs/deployment/server-workers.md
Insbesondere wenn die Anwendung auf **Kubernetes** läuft, werden Sie wahrscheinlich **keine** Worker verwenden wollen, und stattdessen **einen einzelnen Uvicorn-Prozess pro Container** ausführen wollen, aber ich werde Ihnen später in diesem Kapitel mehr darüber erzählen. /// ## Mehrere Worker { #multiple-workers } Sie können mehrere Worker mit der `--workers`-Befehlszeilenoption starten: //// tab | `fastapi`Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Tue Dec 02 17:32:56 GMT 2025 - 8.8K bytes - Click Count (0) -
docs/es/docs/deployment/server-workers.md
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">Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Tue Dec 16 16:33:45 GMT 2025 - 8.5K bytes - Click Count (0) -
docs/en/docs/deployment/server-workers.md
In particular, when running on **Kubernetes** you will probably **not** want to use workers and instead run **a single Uvicorn process per container**, but I'll tell you about it later in that chapter. /// ## Multiple Workers { #multiple-workers } You can start multiple workers with the `--workers` command line option: //// tab | `fastapi` If you use the `fastapi` command: <div class="termy">Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sun Aug 31 09:15:41 GMT 2025 - 8.3K bytes - Click Count (0) -
docs/pt/docs/deployment/server-workers.md
/// ## Vários trabalhadores { #multiple-workers } Você pode iniciar vários trabalhadores com a opção de linha de comando `--workers`: //// tab | `fastapi` Se você usar o comando `fastapi`: <div class="termy"> ```console $ <font color="#4E9A06">fastapi</font> run --workers 4 <u style="text-decoration-style:solid">main.py</u>Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Nov 12 16:23:57 GMT 2025 - 8.6K bytes - Click Count (0) -
docs/ru/docs/deployment/server-workers.md
/// ## Несколько воркеров { #multiple-workers } Можно запустить несколько воркеров с помощью опции командной строки `--workers`: //// tab | `fastapi` Если вы используете команду `fastapi`: <div class="termy"> ```console $ <font color="#4E9A06">fastapi</font> run --workers 4 <u style="text-decoration-style:solid">main.py</u>Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Tue Sep 30 11:37:11 GMT 2025 - 10.6K bytes - Click Count (0) -
internal/logger/target/http/http.go
// If the channel reaches above half capacity // we spawn more workers. The workers spawned // from this main worker routine will exit // once the channel drops below half capacity // and when it's been at least 30 seconds since // we launched a new worker. if mainWorker && len(h.logCh) > cap(h.logCh)/2 { nWorkers := h.workers.Load() if nWorkers < h.maxWorkers { if time.Since(h.lastStarted).Milliseconds() > 10 {
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Aug 29 02:39:48 GMT 2025 - 15.6K bytes - Click Count (0) -
docs/de/docs/deployment/docker.md
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 }
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Tue Dec 02 17:32:56 GMT 2025 - 33.6K bytes - Click Count (0) -
cmd/bucket-replication.go
if (checkOld > 0 && len(p.workers) != checkOld) || n == len(p.workers) || n < 1 { // Either already satisfied or worker count changed while we waited for the lock. return } for len(p.workers) < n { input := make(chan ReplicationWorkerOperation, 10000) p.workers = append(p.workers, input) go p.AddWorker(input, &p.activeWorkers) } for len(p.workers) > n { worker := p.workers[len(p.workers)-1]
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Sep 28 20:59:21 GMT 2025 - 118.2K bytes - Click Count (0) -
cmd/bucket-lifecycle.go
workers = workers[:len(workers)-1] worker <- expiryOp(nil) es.stats.workers.Add(-1) } // Atomically replace workers. es.workers.Store(&workers) } // Worker handles 4 types of expiration tasks. // 1. Expiry of objects, includes regular and transitioned objects // 2. Expiry of noncurrent versions due to NewerNoncurrentVersions
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Aug 29 02:39:48 GMT 2025 - 33.7K bytes - Click Count (0) -
docs/es/docs/deployment/concepts.md
Aquí hay algunas combinaciones y estrategias posibles: * **Uvicorn** con `--workers` * Un administrador de procesos de Uvicorn **escucharía** en la **IP** y **puerto**, y iniciaría **múltiples worker processes de Uvicorn**. * **Kubernetes** y otros sistemas de **contenedor distribuidos**Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Tue Dec 16 16:33:45 GMT 2025 - 20.1K bytes - Click Count (0)