Ljh684/moonnet-lab/examples/rpc_retry

Ljh684/moonnet-lab/examples/rpc_retry does not have a README file

CallOutcome

pub(all) struct CallOutcome {
  attempts : Int
  delivered : Bool
  latency : @Ljh684/moonnet-lab/src/sim.Time
Time
} derive(Eq, @moonbitlang/core/debug.Debug
Debug)

What one call did.

Frame

source

pub(all) enum Frame {
  Request
  Reply
} derive(Eq, @moonbitlang/core/debug.Debug
Debug)

What travels on the wire. The payload type is chosen by the caller; the link does not care what is inside a packet.

Measurement

source

pub(all) struct Measurement {
  calls : Int
  delivered : Int
  mean_attempts : Double
  mean_latency : @Ljh684/moonnet-lab/src/sim.Time
Time
} derive(Eq, @moonbitlang/core/debug.Debug
Debug)

What a row of the table says.

Measurement::to_line

source

fn Measurement::to_line(self : Measurement, loss : Double) -> String

One line of the table.

RpcPolicy

source

pub(all) struct RpcPolicy {
  timeout : @Ljh684/moonnet-lab/src/sim.Time
Time
  attempts : Int
} derive(Eq, @moonbitlang/core/debug.Debug
Debug)

The retry policy under test.

call

source

fn call(sim : @Ljh684/moonnet-lab/src/sim.Sim
Sim, policy : RpcPolicy, uplink : @Ljh684/moonnet-lab/src/net.LinkSpec
LinkSpec, downlink : @Ljh684/moonnet-lab/src/net.LinkSpec
LinkSpec, seed : UInt64) -> CallOutcome

Run one call to completion and report what it cost.

The two links are built from the same seed but carry different names, and the loss decision is mixed with the name - so the request and the reply see unrelated loss patterns, which is what two directions of a real path do.

default_policy

source

fn default_policy() -> RpcPolicy

The policy the table below uses: a 200 ms deadline, at most four attempts.

link_spec

source

fn link_spec(name : String, loss : Double) -> @Ljh684/moonnet-lab/src/net.LinkSpec
LinkSpec

The link a call runs over, so the table below and the tests describe the same path.

measure

source

fn measure(loss : Double, policy : RpcPolicy, seeds : Int) -> Measurement

How a policy fares on a path that drops loss of the packets, over seeds independent calls. This is the table the entry point prints, kept here so it can be asserted by a test rather than only looked at.