- Sort Score
- Num 10 results
- Language All
Results 1 - 10 of 179 for cpus (0.05 seconds)
-
cmd/update.go
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Sep 28 20:59:21 GMT 2025 - 18.9K bytes - Click Count (0) -
docs/tuning/tuned.conf
net.ipv4.tcp_mtu_probing=1 net.ipv4.tcp_base_mss=1280 # Disable ipv6 net.ipv6.conf.all.disable_ipv6=1 net.ipv6.conf.default.disable_ipv6=1 net.ipv6.conf.lo.disable_ipv6=1 [bootloader] # Avoid firing timers for all CPUs at the same time. This is irrelevant for # full nohz systems
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Jul 12 23:31:18 GMT 2024 - 1.9K bytes - Click Count (0) -
docs/es/docs/deployment/server-workers.md
## Resumen { #recap } Puedes usar múltiples worker processes con la opción CLI `--workers` con los comandos `fastapi` o `uvicorn` para aprovechar los **CPUs de múltiples núcleos**, para ejecutar **múltiples procesos en paralelo**.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) -
compat/maven-embedder/src/test/java/org/apache/maven/cli/MavenCliTest.java
assertThrows(IllegalArgumentException.class, () -> cli.calculateDegreeOfConcurrency("XXXC")); int cpus = Runtime.getRuntime().availableProcessors(); assertEquals((int) (cpus * 2.2), cli.calculateDegreeOfConcurrency("2.2C")); assertEquals(1, cli.calculateDegreeOfConcurrency("0.0001C"));
Created: Sun Dec 28 03:35:09 GMT 2025 - Last Modified: Wed Sep 17 10:01:14 GMT 2025 - 30.9K bytes - Click Count (0) -
docs/en/docs/deployment/server-workers.md
## Recap { #recap } You can use multiple worker processes with the `--workers` CLI option with the `fastapi` or `uvicorn` commands to take advantage of **multi-core CPUs**, to run **multiple processes in parallel**. You could use these tools and ideas if you are setting up **your own deployment system** while taking care of the other deployment concepts yourself.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/de/docs/deployment/server-workers.md
## Zusammenfassung { #recap } Sie können mehrere Workerprozesse mit der `--workers`-CLI-Option über die `fastapi`- oder `uvicorn`-Befehle nutzen, um **Multikern-CPUs** auszunutzen und **mehrere Prozesse parallel** auszuführen. Sie könnten diese Tools und Ideen nutzen, wenn Sie **Ihr eigenes Deployment-System** einrichten und sich dabei selbst um die anderen Deployment-Konzepte kümmern.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/pt/docs/deployment/server-workers.md
## Recapitular { #recap } Você pode usar vários processos de trabalho com a opção CLI `--workers` com os comandos `fastapi` ou `uvicorn` para aproveitar as vantagens de **CPUs multi-core** e executar **vários processos em paralelo**. Você pode usar essas ferramentas e ideias se estiver configurando **seu próprio sistema de implantação** enquanto cuida dos outros conceitos de implantação.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/security/README.md
- [PRF](#prf): HMAC-SHA-256 - [AEAD](#aead): AES-256-GCM if the CPU supports AES-NI, ChaCha20-Poly1305 otherwise. More specifically AES-256-GCM is only selected for X86-64 CPUs with AES-NI extension.
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Wed Feb 26 09:25:50 GMT 2025 - 13.8K bytes - Click Count (0) -
cmd/peer-rest-server.go
} info := getLocalServerProperty(globalEndpoints, &r, metrics) return madminServerProperties.NewJSONWith(&info), nil } // GetCPUsHandler - returns CPU info. func (s *peerRESTServer) GetCPUsHandler(_ *grid.MSS) (*grid.JSON[madmin.CPUs], *grid.RemoteErr) { info := madmin.GetCPUs(context.Background(), globalLocalNodeName) return madminCPUs.NewJSONWith(&info), nil }
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Sep 28 20:59:21 GMT 2025 - 53.6K bytes - Click Count (0) -
docs/es/docs/deployment/concepts.md
Por otro lado, si tienes 2 servidores y estás usando **100% de su CPU y RAM**, en algún momento un proceso pedirá más memoria y el servidor tendrá que usar el disco como "memoria" (lo cual puede ser miles de veces más lento), o incluso **colapsar**. O un proceso podría necesitar hacer algún cálculo y tendría que esperar hasta que la CPU esté libre de nuevo.
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)