- Sort Score
- Num 10 results
- Language All
Results 61 - 70 of 256 for cpui (0.02 seconds)
-
README.md
A smaller CPU-only TensorFlow package is also available: ``` pip install tensorflow-cpu ``` To update TensorFlow to the latest version, add the `--upgrade` flag to the commands above. *Nightly binaries are available for testing using the [tf-nightly](https://pypi.python.org/pypi/tf-nightly) and [tf-nightly-cpu](https://pypi.python.org/pypi/tf-nightly-cpu) packages on PyPI.*
Created: Tue Apr 07 12:39:13 GMT 2026 - Last Modified: Thu Apr 02 10:38:57 GMT 2026 - 11.6K bytes - Click Count (0) -
src/main/java/org/codelibs/fess/timer/LoadControlMonitorTarget.java
if (logger.isDebugEnabled()) { logger.debug("Search Engine CPU: {}%", maxCpu); } } catch (final Exception e) { systemHelper.setSearchEngineCpuPercent((short) 0); consecutiveFailures++; if (consecutiveFailures <= 3) { logger.warn("Failed to get search engine CPU stats.", e); } else if (logger.isDebugEnabled()) {
Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Tue Feb 10 04:24:02 GMT 2026 - 3K bytes - Click Count (0) -
docs/ru/docs/deployment/concepts.md
С другой стороны, если у вас 2 сервера и вы используете **100% их CPU и RAM**, в какой‑то момент один процесс попросит больше памяти, и сервер начнёт использовать диск как «память» (что в тысячи раз медленнее) или даже **упадёт**. Или процессу понадобятся вычисления, но ему придётся ждать освобождения CPU.
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 17:56:20 GMT 2026 - 29.5K bytes - Click Count (0) -
docs/zh-hant/docs/deployment/concepts.md
你的伺服器(群)是可以被「消耗/利用」的「資源」,你的程式會使用 CPU 的計算時間,以及可用的 RAM 記憶體。 你想要消耗/利用多少系統資源?直覺上可能會想「不要太多」,但實際上,你大概會希望在「不當機」的前提下「盡可能用多一點」。 如果你花錢租了 3 台伺服器,卻只用了它們少量的 RAM 與 CPU,那你可能是在「浪費金錢」💸、也「浪費伺服器電力」🌎 等。 在那種情況下,可能更好的是只用 2 台伺服器,並以更高的比例使用它們的資源(CPU、記憶體、磁碟、網路頻寬等)。 另一方面,如果你有 2 台伺服器,且你使用了它們「100% 的 CPU 與 RAM」,某個時刻一個行程會要求更多記憶體,伺服器就得用磁碟當作「記憶體」(這可能慢上數千倍),甚至「當機」。或是某個行程需要做計算時,必須等到 CPU 再度空閒。
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Fri Mar 20 17:05:38 GMT 2026 - 16.1K bytes - Click Count (0) -
docs/zh/docs/deployment/concepts.md
您的服务器是一个**资源**,您可以通过您的程序消耗或**利用**CPU 上的计算时间以及可用的 RAM 内存。 您想要消耗/利用多少系统资源? 您可能很容易认为“不多”,但实际上,您可能希望在不崩溃的情况下**尽可能多地消耗**。 如果您支付了 3 台服务器的费用,但只使用了它们的一点点 RAM 和 CPU,那么您可能**浪费金钱** 💸,并且可能 **浪费服务器电力** 🌎,等等。 在这种情况下,最好只拥有 2 台服务器并使用更高比例的资源(CPU、内存、磁盘、网络带宽等)。 另一方面,如果您有 2 台服务器,并且正在使用 **100% 的 CPU 和 RAM**,则在某些时候,一个进程会要求更多内存,并且服务器将不得不使用磁盘作为“内存” (这可能会慢数千倍),甚至**崩溃**。 或者一个进程可能需要执行一些计算,并且必须等到 CPU 再次空闲。
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Fri Mar 20 17:06:37 GMT 2026 - 16.8K bytes - Click Count (0) -
docs/tr/docs/deployment/concepts.md
Öte yandan, 2 server'ınız var ve CPU ile RAM'in **%100**'ünü kullanıyorsanız, bir noktada bir process daha fazla bellek ister; server diski "bellek" gibi kullanmak zorunda kalır (binlerce kat daha yavaş olabilir) ya da hatta **crash** edebilir. Ya da bir process bir hesaplama yapmak ister ve CPU tekrar boşalana kadar beklemek zorunda kalır.
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Fri Mar 20 07:53:17 GMT 2026 - 19.2K bytes - Click Count (0) -
src/main/java/org/codelibs/fess/helper/SystemHelper.java
} /** * Gets the current system CPU usage percentage. * * @return The system CPU usage percentage. */ public short currentSystemCpuPercent() { return getSystemCpuPercent(); } /** * Gets the search engine CPU usage percentage. * * @return The search engine CPU usage percentage. */Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Sat Mar 28 06:59:19 GMT 2026 - 43.2K bytes - Click Count (0) -
docs/debugging/s3-verify/go.mod
github.com/go-ini/ini v1.67.0 // indirect github.com/goccy/go-json v0.10.4 // indirect github.com/google/uuid v1.6.0 // indirect github.com/klauspost/compress v1.17.11 // indirect github.com/klauspost/cpuid/v2 v2.2.9 // indirect github.com/minio/md5-simd v1.1.2 // indirect github.com/pmezard/go-difflib v1.0.0 // indirect github.com/rs/xid v1.6.0 // indirect golang.org/x/crypto v0.36.0 // indirect
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Fri Oct 10 18:57:03 GMT 2025 - 803 bytes - Click Count (0) -
ci/official/envs/linux_arm64
TFCI_BAZEL_COMMON_ARGS="--repo_env=HERMETIC_PYTHON_VERSION=$TFCI_PYTHON_VERSION --repo_env=USE_PYWRAP_RULES=True --config release_arm64_linux" TFCI_BAZEL_TARGET_SELECTING_CONFIG_PREFIX=linux_arm64 # Note: this is not set to "--cpu", because that changes the package name # to tensorflow_cpu. These ARM builds are supposed to have the name "tensorflow" # despite lacking Nvidia CUDA support. TFCI_BUILD_PIP_PACKAGE_WHEEL_NAME_ARG="--repo_env=WHEEL_NAME=tensorflow"
Created: Tue Apr 07 12:39:13 GMT 2026 - Last Modified: Thu Mar 12 16:45:37 GMT 2026 - 1.6K bytes - Click Count (0) -
Vagrantfile
define_opts = { autostart: false }.freeze Vagrant.configure(2) do |config| config.vm.provider 'virtualbox' do |vbox| # Give the box more memory and cpu because our tests are beasts! vbox.memory = Integer(ENV['VAGRANT_MEMORY'] || 8192) vbox.cpus = Integer(ENV['VAGRANT_CPUS'] || 4) # see https://github.com/hashicorp/vagrant/issues/9524 vbox.customize ["modifyvm", :id, "--audio", "none"] endCreated: Wed Apr 08 16:19:15 GMT 2026 - Last Modified: Wed Feb 17 17:41:23 GMT 2021 - 14.9K bytes - Click Count (0)