package exact_test_sampler

Get desktop application:
View/edit binary Protocol Buffers messages

• rpc simulate (stream AnalysisRequest, stream ResultSet)

  exact_test_sampler.proto:48

  message AnalysisRequest

  exact_test_sampler.proto:22

  The initial request for analysis must both the raw data (observations from real benchmarking), and the analysis parameters. Later messages inherit the last `raw_data` or parameters, and usually only include the parameters.

  • optional RawData raw_data = 1

  • optional bytes parameters = 2

    Analysis parameters (returned by `exact_test._group_statistics_in_plan`), pickled into a byte array.

  message ResultSet

  exact_test_sampler.proto:33

  An analysis request receives a stream of result sets as a response. A `ResultSet` is a set of `StatisticValues`, where each reports a bag of simulated Monte Carlo values for a given `statistic_name`.

  • repeated ResultSet.StatisticValues results = 1

• rpc status (StatusRequest, StatusResponse)

  exact_test_sampler.proto:50

  message StatusRequest

  exact_test_sampler.proto:44

  (message has no fields)

  message StatusResponse

  exact_test_sampler.proto:42

  (message has no fields)

A RawData message represents values observed during real benchmarking, for two different implementations (A and B). Best practices would have use wrap the `uint64` values in a message for extensibility, but we expect these repeated fields to be relatively large (thousands of values).

Used in: AnalysisRequest

• repeated uint64 a_values = 1

  Values observed for the A class.

• repeated uint64 b_values = 2

  Values observed for the B class.

Used in: ResultSet

• optional string statistic_name = 1

• repeated double values = 2