Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 2 of 2 for Transfer (0.19 sec)

  1. .bazelrc

    build:rbe_base --remote_executor=grpcs://remotebuildexecution.googleapis.com
    build:rbe_base --remote_timeout=3600
    build:rbe_base --spawn_strategy=remote,worker,standalone,local
    # Attempt to minimize the amount of data transfer between bazel and the remote
    # workers:
    build:rbe_base --remote_download_toplevel
    test:rbe_base --test_env=USER=anon
    
    # TODO(kanglan): Check if we want to merge rbe_linux into rbe_linux_cpu.
    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)
  2. RELEASE.md

        distributing datasets. For this to work, the dispatcher's `work_dir` must be
        accessible from workers. If the worker fails to read from the `work_dir`, it
        falls back to using RPC for dataset graph transfer.
    *   Adds support for a new "distributed_epoch" processing mode. This processing
        mode distributes a dataset across all tf.data workers, instead of having
        each worker process the full dataset. See
    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)
Back to top