Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for refresh (0.19 sec)

  1. ci/official/README.md

    #
    #   Important: because the container is persistent, you cannot change TFCI
    #   variables in between script executions. To forcibly remove the
    #   container and start fresh, run "docker rm -f tf". Removing the container
    #   destroys some temporary bazel data and causes longer builds.
    #
    #   You will need the NVIDIA Container Toolkit for GPU testing:
    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)
  2. RELEASE.md

        prediction-flavored outputs, in addition to the classification-flavored one.
        Building signatures from these allows TF Serving to honor requests using the
        different APIs (Classify, Regress, and Predict). Furthermore,
        `serving_input_receiver_fn()` may now specify alternative subsets of nodes
        that may act as inputs. This allows, for instance, producing a prediction
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Mon Apr 29 19:17:57 GMT 2024
    - 727.7K bytes
    - Viewed (8)
  3. .bazelrc

    build:mkl_aarch64_threadpool --define=build_with_mkl_aarch64=true
    build:mkl_aarch64_threadpool -c opt
    
    # CUDA: This config refers to building CUDA op kernels with nvcc.
    build:cuda --repo_env TF_NEED_CUDA=1
    build:cuda --crosstool_top=@local_config_cuda//crosstool:toolchain
    build:cuda --@local_config_cuda//:enable_cuda
    
    # CUDA: This config refers to building CUDA op kernels with clang.
    build:cuda_clang --config=cuda
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Thu May 02 19:34:20 GMT 2024
    - 52.8K bytes
    - Viewed (2)
Back to top