Get desktop application:
View/edit binary Protocol Buffers messages
A single class.
Used in:
Label or name of the class.
Score for this class (e.g., the probability the item belongs to this class). As per the proto3 default-value semantics, if the score is missing, it should be treated as 0.
Used in:
Model Specification. If version is not specified, will use the latest (numerical) version.
Input data.
Used in:
Effective Model Specification used for classification.
Result of the classification.
Contains one result per input example, in the same order as the input in ClassificationRequest.
Used in: ,
List of classes for a single item (tensorflow.Example).
Used in:
Used in:
Specifies one or more fully independent input Examples. See examples at: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/example/example.proto
Used in:
Specifies one or more independent input Examples, with a common context Example. The common use case for context is to cleanly and optimally specify some features that are common across multiple examples. See example below with a search query as the context and multiple restaurants to perform some inference on. context: { features: { feature: { key : "query" value: { bytes_list: { value: [ "pizza" ] } } } } } examples: { features: { feature: { key : "cuisine" value: { bytes_list: { value: [ "Pizzeria" ] } } } } } examples: { features: { feature: { key : "cuisine" value: { bytes_list: { value: [ "Taqueria" ] } } } } } Implementations of ExampleListWithContext merge the context Example into each of the Examples. Note that feature keys must not be duplicated between the Examples and context Example, or the behavior is undefined. See also: tensorflow/core/example/example.proto https://developers.google.com/protocol-buffers/docs/proto3#maps
Used in:
Inference result, matches the type of request or is an error.
Used in:
Inference request such as classification, regression, etc...
Used in:
Model Specification. If version is not specified, will use the latest (numerical) version. All ModelSpecs in a MultiInferenceRequest must access the same model name.
Signature's method_name. Should be one of the method names defined in third_party/tensorflow/python/saved_model/signature_constants.py. e.g. "tensorflow/serving/classify".
Used in: , ,
Used in:
Identifies the type of the LogCollector we will use to collect these logs.
The prefix to use for the filenames of the logs.
Metadata logged along with the request logs.
Used in:
List of tags used to load the relevant MetaGraphDef from SavedModel.
TODO(b/33279154): Add more metadata as mentioned in the bug.
Configuration for logging query/responses.
Metadata for an inference request such as the model name and version.
Used in: , , , , , , , , , ,
Required servable name.
Optional choice of which version of the model to use. Expected to be left unset in the common case. Should be specified when there is a strong version consistency requirement (e.g. when the model signature changes across versions and requests need to be version-specific). When left unspecified, the system will serve the best available version. This is typically the latest version, though during version transitions, notably when serving on a fleet of instances, may be either the previous or new version.
Use this specific version number.
Use the version associated with the given label.
A named signature to evaluate. If unspecified, the default signature will be used.
Used in:
Inference request containing one or more requests.
Used in:
Inference tasks.
Input data.
Inference request containing one or more responses.
Used in:
List of results; one for each InferenceTask in the request, returned in the same order as the request.
Used in:
PredictRequest specifies which TensorFlow model to run, as well as how inputs are mapped to tensors and how outputs are filtered before returning to user.
Used in: ,
Model Specification. If version is not specified, will use the latest (numerical) version.
Input tensors. Names of input tensor are alias names. The mapping from aliases to real input tensor names is stored in the SavedModel export as a prediction SignatureDef under the 'inputs' field.
Output filter. Names specified are alias names. The mapping from aliases to real output tensor names is stored in the SavedModel export as a prediction SignatureDef under the 'outputs' field. Only tensors specified here will be run/fetched and returned, with the exception that when none is specified, all tensors specified in the named signature will be run/fetched and returned.
Options for streaming requests to control how multiple requests/responses are handled within a single stream.
Client identifier to group requests belonging to a specific entity. Example entities can be product ids, service names, user ids etc. Servers can use this to optimize placement, caching and colocation. TODO(b/329897437): Migrate to client_id in RequestOptions.
Options for PredictRequest.
Used in:
Client identifier to group requests belonging to a specific entity. Example entities can be product ids, service names, user ids etc. Servers can use this to optimize placement, caching and colocation.
Deterministic mode for the request. When specified, model servers will reduce numeric instability based on different mode selections.
Used in:
Only supported in disaggregated serving. When set, the request will be pinned to a fixed decoder slot index that's deterministic across processes.
Response for PredictRequest on successful run.
Used in: ,
Effective Model Specification used to process PredictRequest.
Output tensors.
Used in:
Options only used for streaming requests that control how inputs/ouputs are handled in the stream.
Request state used to handle splitting of requests. NONE is the default when the stream request is not split. SPLIT is used when multiple streamed requests are used to generate a logical request. END_SPLIT should be called for the last split of the logical request. NONE can not be interspersed with SPLIT before END_SPLIT is called. If another request is sent on the same stream after END_SPLIT, it can be any of the RequestState since a new logical request has started. If END_SPLIT is called on its own the behavior is the same as NONE. Some examples with a mix of request states and the logical request. Example 1 : SPLIT SPLIT END_SPLIT Will be treated as a single logical request. Example 2: NONE END_SPLIT NONE Will be treated as three logical requests (1. NONE 2. END_SPLIT, 3. NONE) Example 3: SPLIT SPLIT Invalid because END_SPLIT is never call. Example 4: SPLIT NONE SPLIT END_SPLIT Invalid because is interspersed with SPLIT. Example 5: SPLIT END_SPLIT SPLIT SPLIT END_SPLIT Will be treated as two logical requests (1. SPLIT, END_SPLIT 2. SPLIT, SPLIT, END_SPLIT)
Used in:
Request state used to handle segmentation of requests.
Input tensors split dimensions. Defines the dimension used to split input tensors specified in PredictRequest.inputs. The dimension will be used for concatenation of multiple SPLIT requests. For input tensor in PredictRequest.inputs that are not contained in this map, the tensors from the first SPLIT request will be used. For example, with an original input tensor of [[1, 2, 3, 4], [5, 6, 7, 8]]. For a split dimension of 0 and two requests (SPLIT and END_SPLIT), the input tensors for request 1 should be [1, 2, 3, 4] and request 2 should be be [5, 6, 7, 8]. For a split dimension of 1 and two requests (SPLIT and END_SPLIT), the input tensors for request 1 should be [[1, 2], [5, 6]] and request 2 should be [[3, 4], [7, 8]].
Used in:
Logged model inference request.
Used in:
Regression result for a single item (tensorflow.Example).
Used in:
Used in:
Model Specification. If version is not specified, will use the latest (numerical) version.
Input data.
Used in:
Effective Model Specification used for regression.
Contains one result per input example, in the same order as the input in RegressionRequest.
Used in: ,
Used in: ,
Requests will be logged uniformly at random with this probability. Valid range: [0, 1.0].
Bitwise OR of above attributes
Attributes of requests that can be optionally sampled. Note: Enabling more attributes will increase logging storage requirements.
Used in:
Used in:
Model Specification. If version is not specified, will use the latest (numerical) version.
Tensors to be fed in the step. Each feed is a named tensor.
Fetches. A list of tensor names. The caller expects a tensor to be returned for each fetch[i] (see RunResponse.tensor). The order of specified fetches does not change the execution order.
Target Nodes. A list of node names. The named nodes will be run to but their outputs will not be fetched.
If true, treat names in feed/fetch/target as alias names than actual tensor names (that appear in the TF graph). Alias names are resolved to actual names using `SignatureDef` in SavedModel associated with the model.
Used in:
Effective Model Specification used for session run.
NOTE: The order of the returned tensors may or may not match the fetch order specified in RunRequest.