- Sort Score
- Num 10 results
- Language All
Results 51 - 60 of 256 for cpui (0.54 seconds)
-
docs/metrics/prometheus/list.md
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Tue Aug 12 18:20:36 GMT 2025 - 43.4K bytes - Click Count (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.Created: Tue Apr 07 12:39:13 GMT 2026 - Last Modified: Mon Jun 30 16:38:59 GMT 2025 - 4K bytes - Click Count (1) -
cmd/metrics-resource.go
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Fri Oct 10 18:57:03 GMT 2025 - 17.2K bytes - Click Count (0) -
RELEASE.md
* `tf.raw_ops.Bucketize` op on CPU. * `tf.where` op for data types `tf.int32`/`tf.uint32`/`tf.int8`/`tf.uint8`/`tf.int64`. * `tf.random.normal` op for output data type `tf.float32` on CPU. * `tf.random.uniform` op for output data type `tf.float32` on CPU. * `tf.random.categorical` op for output data type `tf.int64` on CPU. * `tensorflow.experimental.tensorrt`:Created: Tue Apr 07 12:39:13 GMT 2026 - Last Modified: Mon Mar 30 18:31:38 GMT 2026 - 746.5K bytes - Click Count (3) -
docs/ko/docs/deployment/server-workers.md
또한 각 프로세스의 **PID**도 확인할 수 있는데, 상위 프로세스(이것이 **프로세스 관리자**)의 PID는 `27365`이고, 각 워커 프로세스의 PID는 `27368`, `27369`, `27370`, `27367`입니다. ## 배포 개념들 { #deployment-concepts } 여기서는 여러 **워커**를 사용해 애플리케이션 실행을 **병렬화**하고, CPU의 **다중 코어**를 활용하며, **더 많은 요청**을 제공할 수 있는 방법을 살펴봤습니다. 위의 배포 개념 목록에서 워커를 사용하는 것은 주로 **복제** 부분에 도움이 되고, **재시작**에도 약간 도움이 되지만, 나머지 항목들도 여전히 신경 써야 합니다: * **보안 - HTTPS** * **서버 시작 시 실행** * ***재시작*** * 복제(실행 중인 프로세스 수)Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Fri Mar 20 14:06:26 GMT 2026 - 8.7K bytes - Click Count (0) -
tensorflow/c/README.md
- Nightly builds: - [Linux CPU-only](https://storage.googleapis.com/tensorflow-nightly/github/tensorflow/lib_package/libtensorflow-cpu-linux-x86_64.tar.gz) - [Linux GPU](https://storage.googleapis.com/tensorflow-nightly/github/tensorflow/lib_package/libtensorflow-gpu-linux-x86_64.tar.gz)
Created: Tue Apr 07 12:39:13 GMT 2026 - Last Modified: Tue Oct 23 01:38:30 GMT 2018 - 539 bytes - Click Count (0) -
docs/debugging/s3-verify/go.sum
github.com/klauspost/compress v1.17.11/go.mod h1:pMDklpSncoRMuLFrf1W9Ss9KT+0rH90U12bZKk7uwG0= github.com/klauspost/cpuid/v2 v2.0.1/go.mod h1:FInQzS24/EEf25PyTYn52gqo7WaD8xa0213Md/qVLRg= github.com/klauspost/cpuid/v2 v2.2.9 h1:66ze0taIn2H33fBvCkXuv9BmCwDfafmiIVpKV9kKGuY= github.com/klauspost/cpuid/v2 v2.2.9/go.mod h1:rqkxqrZ1EhYM9G+hXH7YdowN5R5RGN6NK4QwQ3WMXF8= github.com/minio/md5-simd v1.1.2 h1:Gdi1DZK69+ZVMoNHRXJyNcxrMA4dSxoYHZSQbirFg34=
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Thu Apr 17 11:45:33 GMT 2025 - 3K bytes - Click Count (0) -
cmd/metrics-realtime.go
} if types.Contains(madmin.MetricsCPU) { m.Aggregated.CPU = &madmin.CPUMetrics{ CollectedAt: UTCNow(), } cm, err := c.Times(false) if err != nil { m.Errors = append(m.Errors, fmt.Sprintf("%s: %v (cpuTimes)", byHostName, err.Error())) } else { // not collecting per-cpu stats, so there will be only one element if len(cm) == 1 { m.Aggregated.CPU.TimesStat = &cm[0] } else {
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Sun Sep 28 20:59:21 GMT 2025 - 6.3K bytes - Click Count (0) -
src/main/java/org/codelibs/fess/app/web/api/admin/stats/ApiAdminStatsAction.java
/** * Data transfer object representing process CPU statistics. */ public static class ProcessCpuObj { /** * Default constructor. */ public ProcessCpuObj() { // Default constructor } /** CPU usage percentage for the process. */ public short percent; /** Total CPU time used by the process in milliseconds. */Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Thu Jul 17 08:28:31 GMT 2025 - 19.7K bytes - Click Count (0) -
docs/uk/docs/deployment/concepts.md
З іншого боку, якщо у вас 2 сервери і ви використовуєте **100% їхнього CPU та RAM**, у певний момент якийсь процес попросить більше пам'яті, і сервер муситиме використати диск як «пам'ять» (що може бути у тисячі разів повільнішим) або навіть **впасти**. Або процесу знадобляться обчислення, і він чекатиме, доки CPU знову звільниться.
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 18:27:41 GMT 2026 - 29.6K bytes - Click Count (0)