- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 273 for processos (0.22 sec)
-
docs/pt/docs/deployment/docker.md
Um contêiner está rodando enquanto o **processo principal** (comando ou programa) estiver rodando. Um contêiner normalmente tem um **único processo**, mas também é possível iniciar sub-processos a partir do processo principal, e dessa forma você terá **vários processos** no mesmo contêiner. Mas não é possível ter um contêiner rodando sem **pelo menos um processo rodando**. Se o processo principal parar, o contêiner também para.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 37.4K bytes - Viewed (0) -
docs/pt/docs/alternatives.md
!!! check "**FastAPI** recomenda isso para" O principal servidor web para rodar aplicações **FastAPI**. Você pode combinar ele com o Gunicorn, para ter um servidor multi-processos assíncrono. Verifique mais detalhes na seção [Deployment](deployment/index.md){.internal-link target=_blank}. ## Performance e velocidade
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 25.5K bytes - Viewed (0) -
build-logic/cleanup/src/main/java/gradlebuild/cleanup/services/KillLeakingJavaProcesses.java
* Only kill local Gradle processes (classpath in checkout directory). * Not clean up global Gradle processes (i.e. classpath in ~/.gradle/...). */ KILL_LEAKED_PROCESSES_FROM_PREVIOUS_BUILDS, /** * Run at the end of each build. Kill potentially leaked processes in the current build.
Java - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Apr 26 09:46:00 GMT 2024 - 11.3K bytes - Viewed (0) -
callbacks.go
match func(*DB) bool handler func(*DB) processor *processor } func (cs *callbacks) Create() *processor { return cs.processors["create"] } func (cs *callbacks) Query() *processor { return cs.processors["query"] } func (cs *callbacks) Update() *processor { return cs.processors["update"] } func (cs *callbacks) Delete() *processor { return cs.processors["delete"] }
Go - Registered: Sun May 05 09:35:13 GMT 2024 - Last Modified: Tue Mar 26 03:33:36 GMT 2024 - 8.6K bytes - Viewed (1) -
.teamcity/test-buckets.json
"toolchains-jvm-shared", "docs-asciidoctor-extensions-base", "internal-instrumentation-processor", "security", "input-tracking", "base-ide-plugins" ] }, { "parallelizationMethod":{ "name":"TestDistribution" }, "subprojects":[ "testing-jvm", "worker-processes", "files", "java-language-extensions", "build-cache-packaging",
Json - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon May 06 14:29:38 GMT 2024 - 49.9K bytes - Viewed (0) -
docs/en/docs/async.md
--- In this scenario of the parallel burgers, you are a computer / program 🤖 with two processors (you and your crush), both waiting 🕙 and dedicating their attention ⏯ to be "waiting on the counter" 🕙 for a long time. The fast food store has 8 processors (cashiers/cooks). While the concurrent burgers store might have had only 2 (one cashier and one cook).
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 23K bytes - Viewed (0) -
analysis/analysis-api-fir/src/org/jetbrains/kotlin/analysis/api/fir/components/KtFirSymbolDeclarationOverridesProvider.kt
declaration: FirDeclaration, processor: (FirCallableDeclaration) -> Unit ) = when (declaration) { is FirSimpleFunction -> processOverriddenFunctions(declaration.symbol) { symbol -> processor.invoke(symbol.fir) ProcessorAction.NEXT } is FirProperty -> processOverriddenProperties(declaration.symbol) { symbol -> processor.invoke(symbol.fir) ProcessorAction.NEXT
Plain Text - Registered: Fri Apr 26 08:18:10 GMT 2024 - Last Modified: Fri Mar 22 14:22:10 GMT 2024 - 9.6K bytes - Viewed (0) -
docs/en/docs/deployment/concepts.md
### Multiple Processes - An Example In this example, there's a **Manager Process** that starts and controls two **Worker Processes**. This Manager Process would probably be the one listening on the **port** in the IP. And it would transmit all the communication to the worker processes.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 18K bytes - Viewed (0) -
docs/en/docs/deployment/server-workers.md
The only new option here is `--workers` telling Uvicorn to start 4 worker processes. You can also see that it shows the **PID** of each process, `27365` for the parent process (this is the **process manager**) and one for each worker process: `27368`, `27369`, `27370`, and `27367`. ## Deployment Concepts
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 9.1K bytes - Viewed (0) -
architecture/runtimes.md
gradlew --> daemon tapi --> daemon worker["Worker process"] daemon --> worker worker2["Worker process"] daemon --> worker2 worker3["Worker process"] daemon --> worker3 ``` These are all Java processes. Each process has a corresponding "runtime". All source code in Gradle is written to target one or more of these runtimes.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 06:42:46 GMT 2024 - 2.3K bytes - Viewed (0)