Search Options

Results per page
Sort
Preferred Languages
Advance

Results 11 - 20 of 40 for GPU (0.01 sec)

  1. configure.py

            (environ_cp.get('TF_NEED_ROCM', None) == '1')):
          test_and_build_filters += ['-no_windows_gpu', '-no_gpu']
        else:
          test_and_build_filters.append('-gpu')
      elif is_macos():
        test_and_build_filters += ['-gpu', '-nomac', '-no_mac', '-mac_excluded']
      elif is_linux():
        if ((environ_cp.get('TF_NEED_CUDA', None) == '1') or
            (environ_cp.get('TF_NEED_ROCM', None) == '1')):
    Registered: Tue Sep 09 12:39:10 UTC 2025
    - Last Modified: Wed Apr 30 15:18:54 UTC 2025
    - 48.3K bytes
    - Viewed (0)
  2. ci/official/libtensorflow.sh

    # limitations under the License.
    # ==============================================================================
    source "${BASH_SOURCE%/*}/utilities/setup.sh"
    
    # Record GPU count and CUDA version status
    if [[ "$TFCI_NVIDIA_SMI_ENABLE" == 1 ]]; then
      tfrun nvidia-smi
    fi
    
    # Update the version numbers for Nightly only
    if [[ "$TFCI_NIGHTLY_UPDATE_VERSION_ENABLE" == 1 ]]; then
    Registered: Tue Sep 09 12:39:10 UTC 2025
    - Last Modified: Fri Jan 24 20:17:08 UTC 2025
    - 2K bytes
    - Viewed (0)
  3. 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
    Registered: Tue Sep 09 12:39:10 UTC 2025
    - Last Modified: Wed Oct 16 16:10:43 UTC 2024
    - 9.6K bytes
    - Viewed (0)
  4. tensorflow/c/c_api_experimental.cc

      // threadpool of GPU event mgr, as that can trigger more callbacks to be
      // scheduled on that same threadpool, causing a deadlock in cases where the
      // caller of event_mgr->ThenExecute() blocks on the completion of the callback
      // (as in the case of ConstOp kernel creation on GPU, which involves copying a
      // CPU tensor to GPU).
    Registered: Tue Sep 09 12:39:10 UTC 2025
    - Last Modified: Mon Aug 18 03:53:25 UTC 2025
    - 29.5K bytes
    - Viewed (0)
  5. ci/official/README.md

    You may invoke a CI script of your choice by following these instructions:
    
    ```bash
    cd tensorflow-git-dir
    
    # Here is a single-line example of running a script on Linux to build the
    # GPU version of TensorFlow for Python 3.12, using the public TF bazel cache and
    # a local build cache:
    TFCI=py312,linux_x86_cuda,public_cache,disk_cache ci/official/wheel.sh
    
    Registered: Tue Sep 09 12:39:10 UTC 2025
    - Last Modified: Thu Feb 01 03:21:19 UTC 2024
    - 8K bytes
    - Viewed (0)
  6. ci/official/wheel.sh

    # limitations under the License.
    # ==============================================================================
    source "${BASH_SOURCE%/*}/utilities/setup.sh"
    
    # Record GPU count and CUDA version status
    if [[ "$TFCI_NVIDIA_SMI_ENABLE" == 1 ]]; then
      tfrun nvidia-smi
    fi
    
    # Update the version numbers for Nightly only
    if [[ "$TFCI_NIGHTLY_UPDATE_VERSION_ENABLE" == 1 ]]; then
    Registered: Tue Sep 09 12:39:10 UTC 2025
    - Last Modified: Mon Mar 03 17:29:53 UTC 2025
    - 3.8K bytes
    - Viewed (0)
  7. .github/workflows/build.yml

            with:
              api-level: ${{ matrix.api-level }}
              arch: ${{ matrix.api-level == '34' && 'x86_64' || 'x86' }}
              force-avd-creation: false
              emulator-options: -no-window -gpu swiftshader_indirect -noaudio -no-boot-anim -camera-back none
              disable-animations: false
              script: echo "Generated AVD snapshot for caching."
    
          - name: Run Tests
    Registered: Fri Sep 05 11:42:10 UTC 2025
    - Last Modified: Thu Aug 21 07:15:58 UTC 2025
    - 18.1K bytes
    - Viewed (0)
  8. docs/en/docs/advanced/events.md

    And then, right after the `yield`, we unload the model. This code will be executed **after** the application **finishes handling requests**, right before the *shutdown*. This could, for example, release resources like memory or a GPU.
    
    /// tip
    
    The `shutdown` would happen when you are **stopping** the application.
    
    Maybe you need to start a new version, or you just got tired of running it. 🤷
    
    ///
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 09:15:41 UTC 2025
    - 7.9K bytes
    - Viewed (0)
  9. docs/pt/docs/advanced/events.md

    E então, logo após o `yield`, descarregaremos o modelo. Esse código será executado **após** a aplicação **terminar de lidar com as requisições**, pouco antes do *encerramento*. Isso poderia, por exemplo, liberar recursos como memória ou GPU.
    
    /// tip | Dica
    
    O `shutdown` aconteceria quando você estivesse **encerrando** a aplicação.
    
    Talvez você precise inicializar uma nova versão, ou apenas cansou de executá-la. 🤷
    
    ///
    
    ### Função _lifespan_
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Mon Nov 18 02:25:44 UTC 2024
    - 8.5K bytes
    - Viewed (0)
  10. docs/es/docs/advanced/events.md

    /// tip | Consejo
    
    El `shutdown` ocurriría cuando estás **deteniendo** la aplicación.
    
    Quizás necesites iniciar una nueva versión, o simplemente te cansaste de ejecutarla. 🤷
    
    ///
    
    ### Función de Lifespan
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Mon Dec 30 18:26:57 UTC 2024
    - 8.2K bytes
    - Viewed (0)
Back to top