Get desktop application:
View/edit binary Protocol Buffers messages
Configuration for a tf.data service DispatchServer. Next id: 10
Used in:
The port for the dispatcher to bind to. A value of 0 indicates that the dispatcher may bind to any available port.
The protocol for the dispatcher to use when connecting to workers.
A work directory to use for storing dispatcher state, and for recovering during restarts. The empty string indicates not to use any work directory.
Whether to run in fault tolerant mode, where dispatcher state is saved across restarts. Requires that `work_dir` is nonempty.
(Optional.) If the job uses auto-sharding, it needs to specify a fixed list of worker addresses that will register with the dispatcher. The worker addresses should be in the format "host" or "host:port", where "port" is an integer, named port, or %port% to match any port.
(Optional.) tf.data service deployment mode. Supported values are "REMOTE", "COLOCATED", and "HYBRID". If unspecified, it is assumed to be "REMOTE".
How often the dispatcher should scan through to delete old and unused jobs. A value of 0 indicates that the decision should be left up to the runtime.
How long a job needs to be unused before it becomes a candidate for garbage collection. A value of -1 indicates that jobs should never be garbage collected. A value of 0 indicates that the decision should be left up to the runtime.
How long to wait before garbage-collecting a client that hasn't heartbeated to the dispatcher. A value of 0 indicates that the timeout should be left to the runtime.
This stores the metadata information present in each snapshot record.
Stores the fingerprint of the graph that describes the dataset that is snapshotted.
Run ID that this snapshot corresponds to.
Time when we started creating this snapshot.
Version of the snapshot data file format.
A list of tensor dtype corresponding to each element of the snapshot.
The number of elements in the snapshot.
Each SnapshotRecord represents one batch of pre-processed input data. A batch consists of a list of tensors that we encode as TensorProtos. This message doesn't store the structure of the batch.
Metadata for all the tensors in a Snapshot Record.
Metadata for a single tensor in the Snapshot Record.
Used in:
Number of uncompressed bytes used to store the tensor representation.
Configuration for a tf.data service WorkerServer. Next id: 12
Used in:
The port for the worker to bind to. A value of 0 indicates that the worker may bind to any available port.
The protocol for the worker to use when connecting to the dispatcher.
The address of the dispatcher to register with.
The address of the worker server. The substring "%port%", if specified, will be replaced with the worker's bound port. This is useful when the port is set to `0`.
Tags attached to the worker. This allows reading from selected workers. For example, by applying a "COLOCATED" tag, tf.data service is able to read from the local tf.data worker if one exists, then from off-TF-host workers, to avoid cross-TF-host reads.
How often the worker should heartbeat to the master. A value of 0 indicates that the decision should be left up to the runtime.
How long to retry requests to the dispatcher before giving up and reporting an error. A value of 0 indicates that the decision should be left up to the runtime.
The protocol for the worker to use when transferring data to clients.
The data transfer address of the worker server. The substring "%port%", if specified, will be replaced with the worker's bound port. This is useful when the port is set to `0`.
Maximum size of the cross-trainer cache in bytes. If enabled, make sure your training job provides sufficient memory resources.
When shutting down a worker, how long to wait for the gRPC server to process the final requests. This is used to achieve clean shutdown in unit tests.