- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 77 for cpus (0.13 sec)
-
internal/kms/kms.go
// is specified. It is empty if the KMS does not support // a default key. DefaultKey string // Details provides more details about the KMS endpoint status. // including uptime, version and available CPUs. // Could be more in future. Details kes.State } // DEK is a data encryption key. It consists of a // plaintext-ciphertext pair and the ID of the key // used to generate the ciphertext. //
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Mar 01 21:09:42 GMT 2024 - 4.6K bytes - Viewed (0) -
docs/en/docs/deployment/server-workers.md
## Recap You can use **Gunicorn** (or also Uvicorn) as a process manager with Uvicorn workers 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.
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) -
cmd/metrics-v3-system-cpu.go
sysCPUAvgIdleMD = NewGaugeMD(sysCPUAvgIdle, "Average CPU idle time") sysCPUAvgIOWaitMD = NewGaugeMD(sysCPUAvgIOWait, "Average CPU IOWait time") sysCPULoadMD = NewGaugeMD(sysCPULoad, "CPU load average 1min") sysCPULoadPercMD = NewGaugeMD(sysCPULoadPerc, "CPU load average 1min (percentage)") sysCPUNiceMD = NewGaugeMD(sysCPUNice, "CPU nice time") sysCPUStealMD = NewGaugeMD(sysCPUSteal, "CPU steal time")
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Apr 23 23:56:12 GMT 2024 - 3K bytes - Viewed (0) -
Dockerfile.release.old_cpu
Harshavardhana <******@****.***> 1711791711 -0700
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Mar 30 09:41:56 GMT 2024 - 2.8K bytes - Viewed (0) -
SECURITY.md
### Hardware attacks Physical GPUs or TPUs can also be the target of attacks. [Published research](https://scholar.google.com/scholar?q=gpu+side+channel) shows that it might be possible to use side channel attacks on the GPU to leak data from other running models or processes in the same system. GPUs can also have implementation bugs that might allow attackers to leave malicious code running
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Sun Oct 01 06:06:35 GMT 2023 - 9.6K bytes - Viewed (0) -
ci/official/README.md
- Different Python versions - Linux, MacOS, and Windows machines (these pool definitions are internal) - x86 and arm64 - CPU-only, or with NVIDIA CUDA support (Linux only), or with TPUs ## How to Test Your Changes to TensorFlow You may check how your changes will affect TensorFlow by: 1. Creating a PR and observing the presubmit test results
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Feb 01 03:21:19 GMT 2024 - 8K bytes - Viewed (0) -
.github/bot_config.yml
Therefore on any CPU that does not have these instruction sets, either CPU or GPU version of TF will fail to load. Apparently, your CPU model does not support AVX instruction sets. You can still use TensorFlow with the alternatives given below: * Try Google Colab to use TensorFlow.
Others - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Tue Oct 17 11:48:07 GMT 2023 - 4K bytes - Viewed (0) -
manifests/charts/gateway/files/profile-demo.yaml
global: proxy: resources: requests: cpu: 10m memory: 40Mi pilot: autoscaleEnabled: false traceSampling: 100 resources: requests: cpu: 10m memory: 100Mi gateways: istio-egressgateway: autoscaleEnabled: false resources: requests: cpu: 10m memory: 40Mi istio-ingressgateway: autoscaleEnabled: false
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 2.1K bytes - Viewed (0) -
manifests/charts/istio-operator/files/profile-demo.yaml
global: proxy: resources: requests: cpu: 10m memory: 40Mi pilot: autoscaleEnabled: false traceSampling: 100 resources: requests: cpu: 10m memory: 100Mi gateways: istio-egressgateway: autoscaleEnabled: false resources: requests: cpu: 10m memory: 40Mi istio-ingressgateway: autoscaleEnabled: false
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 2.1K bytes - Viewed (0) -
manifests/charts/ztunnel/files/profile-demo.yaml
global: proxy: resources: requests: cpu: 10m memory: 40Mi pilot: autoscaleEnabled: false traceSampling: 100 resources: requests: cpu: 10m memory: 100Mi gateways: istio-egressgateway: autoscaleEnabled: false resources: requests: cpu: 10m memory: 40Mi istio-ingressgateway: autoscaleEnabled: false
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 2.1K bytes - Viewed (0)