Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 78 for workerCh (0.04 sec)

  1. 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]
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Sep 28 20:59:21 UTC 2025
    - 118.2K bytes
    - Viewed (0)
  2. cmd/bucket-replication-utils.go

    type replicationResyncer struct {
    	// map of bucket to their resync status
    	statusMap      map[string]BucketReplicationResyncStatus
    	workerSize     int
    	resyncCancelCh chan struct{}
    	workerCh       chan struct{}
    	sync.RWMutex
    }
    
    const (
    	replicationDir      = ".replication"
    	resyncFileName      = "resync.bin"
    	resyncMetaFormat    = 1
    	resyncMetaVersionV1 = 1
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Sep 28 20:59:21 UTC 2025
    - 26.1K bytes
    - Viewed (0)
  3. 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`
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Tue Dec 02 17:32:56 UTC 2025
    - 8.8K bytes
    - Viewed (0)
  4. 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">
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Tue Dec 16 16:33:45 UTC 2025
    - 8.5K bytes
    - Viewed (0)
  5. 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">
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sun Aug 31 09:15:41 UTC 2025
    - 8.3K bytes
    - Viewed (0)
  6. 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>
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Nov 12 16:23:57 UTC 2025
    - 8.6K bytes
    - Viewed (0)
  7. 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>
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Tue Sep 30 11:37:11 UTC 2025
    - 10.6K bytes
    - Viewed (0)
  8. docs/en/docs/deployment/concepts.md

    Here are some possible combinations and strategies:
    
    * **Uvicorn** with `--workers`
        * One Uvicorn **process manager** would listen on the **IP** and **port**, and it would start **multiple Uvicorn worker processes**.
    * **Kubernetes** and other distributed **container systems**
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sun Aug 31 09:15:41 UTC 2025
    - 18.6K bytes
    - Viewed (1)
  9. 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**
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Tue Dec 16 16:33:45 UTC 2025
    - 20.1K bytes
    - Viewed (0)
  10. docs/en/docs/deployment/docker.md

    And if you need to have multiple workers, you can simply use the `--workers` command line option.
    
    /// note | Technical Details
    
    The Docker image was created when Uvicorn didn't support managing and restarting dead workers, so it was needed to use Gunicorn with Uvicorn, which added quite some complexity, just to have Gunicorn manage and restart the Uvicorn worker processes.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sat Sep 20 12:58:04 UTC 2025
    - 29.5K bytes
    - Viewed (1)
Back to top