package grpc.testing

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

service BenchmarkService

services.proto:25

service ReconnectService

test.proto:76

A service used to control reconnect server.

service ReportQpsScenarioService

services.proto:72

service TestService

test.proto:28

A simple service to test the various types of RPCs and experiment with performance with various types of payload.

service UnimplementedService

test.proto:70

A simple service NOT implemented at servers so clients can test for that case.

service WorkerService

services.proto:48

message BoolValue

messages.proto:25

TODO(dgq): Go back to using well-known types once https://github.com/grpc/grpc/issues/6980 has been fixed. import "google/protobuf/wrappers.proto";

Used in: ResponseParameters, SimpleRequest, StreamingInputCallRequest

message ByteBufferParams

payloads.proto:19

Used in: PayloadConfig

message ChannelArg

control.proto:70

Used in: ClientConfig, ServerConfig

message ClientConfig

control.proto:78

Used in: ClientArgs, Scenario

message ClientStats

stats.proto:61

Used in: ClientStatus, ScenarioResult

enum ClientType

control.proto:22

Used in: ClientConfig

message ClosedLoopParams

control.proto:54

Once an RPC finishes, immediately start a new one. No configuration parameters needed.

Used in: LoadParams

(message has no fields)

message ComplexProtoParams

payloads.proto:29

TODO (vpai): Fill this in once the details of complex, representative protos are decided

Used in: PayloadConfig

(message has no fields)

message EchoStatus

messages.proto:48

A protobuf representation for grpc status. This is used by test clients to specify a status that the server should attempt to return.

Used in: SimpleRequest, StreamingOutputCallRequest

message Empty

empty.proto:28

An empty message that you can re-use to avoid defining duplicated empty messages in your project. A typical example is to use it as argument or the return value of a service API. For instance: service Foo { rpc Bar (grpc.testing.Empty) returns (grpc.testing.Empty) { }; };

Used as request type in: ReconnectService.Stop, TestService.EmptyCall, TestService.UnimplementedCall, UnimplementedService.UnimplementedCall

Used as response type in: ReconnectService.Start, TestService.EmptyCall, TestService.UnimplementedCall, UnimplementedService.UnimplementedCall

(message has no fields)

message HistogramData

stats.proto:47

Histogram data based on grpc/support/histogram.c

Used in: ClientStats, ScenarioResult

message HistogramParams

stats.proto:41

Histogram params based on grpc/support/histogram.c

Used in: ClientConfig

message LoadParams

control.proto:56

Used in: ClientConfig

message Mark

control.proto:116

Request current stats

Used in: ClientArgs, ServerArgs

message Payload

messages.proto:38

A block of data, to simply increase gRPC message size.

Used in: SimpleRequest, SimpleResponse, StreamingInputCallRequest, StreamingOutputCallRequest, StreamingOutputCallResponse

message PayloadConfig

payloads.proto:34

Used in: ClientConfig, ServerConfig

enum PayloadType

messages.proto:32

DEPRECATED, don't use. To be removed shortly. The type of payload that should be returned.

Used in: Payload, SimpleRequest, StreamingOutputCallRequest

message PoissonParams

control.proto:47

Parameters of poisson process distribution, which is a good representation of activity coming in from independent identical stationary sources.

Used in: LoadParams

message RequestResultCount

stats.proto:56

Used in: ClientStats, ScenarioResult

message ResponseParameters

messages.proto:117

Configuration for a particular response.

Used in: StreamingOutputCallRequest

enum RpcType

control.proto:37

Used in: ClientConfig

message Scenario

control.proto:186

A single performance scenario: input to qps_json_driver

Used in: ScenarioResult, Scenarios

message ScenarioResultSummary

control.proto:212

Basic summary that can be computed from ClientStats and ServerStats once the scenario has finished.

Used in: ScenarioResult

message Scenarios

control.proto:206

A set of scenarios to be run with qps_json_driver

message SecurityParams

control.proto:64

presence of SecurityParams implies use of TLS

Used in: ClientConfig, ServerConfig

message ServerConfig

control.proto:128

Used in: Scenario, ServerArgs

message ServerStats

stats.proto:19

Used in: ScenarioResult, ServerStatus

enum ServerType

control.proto:30

Used in: ServerConfig

message SimpleProtoParams

payloads.proto:24

Used in: PayloadConfig

message SimpleRequest

messages.proto:54

Unary request.

Used as request type in: BenchmarkService.StreamingBothWays, BenchmarkService.StreamingCall, BenchmarkService.StreamingFromClient, BenchmarkService.StreamingFromServer, BenchmarkService.UnaryCall, TestService.CacheableUnaryCall, TestService.UnaryCall

message SimpleResponse

messages.proto:86

Unary response, as configured by the request.

Used as response type in: BenchmarkService.StreamingBothWays, BenchmarkService.StreamingCall, BenchmarkService.StreamingFromClient, BenchmarkService.StreamingFromServer, BenchmarkService.UnaryCall, TestService.CacheableUnaryCall, TestService.UnaryCall

message StreamingOutputCallRequest

messages.proto:133

Server-streaming request.

Used as request type in: TestService.FullDuplexCall, TestService.HalfDuplexCall, TestService.StreamingOutputCall

message StreamingOutputCallResponse

messages.proto:152

Server-streaming response, as configured by the request and parameters.

Used as response type in: TestService.FullDuplexCall, TestService.HalfDuplexCall, TestService.StreamingOutputCall

message Void

control.proto:182

Used as request type in: WorkerService.QuitWorker

Used as response type in: ReportQpsScenarioService.ReportScenario, WorkerService.QuitWorker

(message has no fields)