Skip to content

Latest commit

 

History

History
152 lines (85 loc) · 3.95 KB

eval.md

File metadata and controls

152 lines (85 loc) · 3.95 KB

Evaluation for sending

The evaluation parameters are updated once. Please refer the benchmarks for the latest parameters. But the documentation can still help to understand what is benchmarked for a particular benchmark.

Communication additional payload for ID

164 B

Steps:

  1. Run eval-gen-pk-sk and follow the output to set envs for the sender and EEMS
  2. Run eval-eems-for-send
  3. Run eval-msg-id-size and get the result from the output

Time of ID generation

Message body size: $2^3$ - $2^{13}$ (B)

Local gRPC is set up for gen_id. Time for every entity is evaluated separately for gen_id_by_entities.

Steps:

  1. Run eval-gen-pk-sk and follow the output to set envs for the sender and EEMS
  2. Run eval-eems-for-send
  3. Run cargo bench --bench gen_id and get the result from the output
  4. Run cargo bench --bench gen_id_by_entities and get the result from the output

Time of message verification

Message body size: $2^3$ - $2^{13}$ and 1300 - (=)4000 (step by 300) (B)

Steps:

  1. Run eval-gen-pk-sk and follow the output to set envs for the sender and EEMS
  2. Run eval-eems-for-send
  3. Run cargo bench --bench verify_msg and get the result from the output

Time of MSP ID shuffle

Message number (Vector size): 1, 2, 5, 10, 12 * 3600s * 11/s

Steps:

  1. Run cargo bench --bench shuffle_id and get the result from the output

Communication payload for ID shares

For 2 shares in total: 5858 B

The MAC is 2 * 28 B. Since we use BigUint to use integer addition as the plus operation, the MAC size can differ with at most 1 B, which should be fine to ignore.

Including the MAC: 11482 B

Steps:

  1. Run eval-id-share-size and get the result from the output

Time of ID share generation

Steps:

  1. Run cargo bench --bench gen_id_shares and get the result from the output

Time of MSP update

Steps:

  1. Run cargo bench --bench update_msp and get the result from the output

Time of MSP comparison

Steps:

  1. Run cargo bench --bench msp_compare and get the result from the output

Time of reporter MAC generation

Steps:

  1. Run cargo bench --bench gen_mac and get the result from the output

Time of MSP verify MAC

Steps:

  1. Run cargo bench --bench verify_mac and get the result from the output

Time of EEMS comparison information generation (DCF & gamma)

Steps:

  1. Run cargo bench --bench gen_compare and get the result from the output

Payload size of EEMS comparison information (DCF & gamma)

5143B for every item

Steps:

  1. Run cargo run --bin eval-compare-size and get the result from the output

Time of EEMS sourcing

Steps:

  1. Run cargo bench --bench seek_source and get the result from the output

seek_source raw log: seek_source.log

Total time of send and recv

  1. Run eval-gen-pk-sk and follow the output to set envs for the sender and EEMS. Additionally set envs for the receiver.
  2. Run eval-eems-for-send
  3. Run cargo bench --bench gen_recv_msg and get the result from the output

gen_recv_msg raw log: gen_recv_msg.log