Skip to content

[Benchmark] [Robust-ECDSA] Generic Robust-Based ECDSA Benchmark Issue #140

@SimonRastikian

Description

@SimonRastikian

Background

We would like to benchmark the Robust-Based ECDSA as we have little objective measurement tools.

User Story

The details of how to benchmark should be described in multiple issues explaining:

How to simulate participants independently in the twtwoo phases (Presign, Sign)
How to measure the time taken by a single (real) participant in the two phases (Presign, Sign)
What to change in the code to be able to add latency
How to measure the computation time per participant
How to measure the amount of data transmitted
How to measure the size of storage in between phases

Acceptance Criteria

The benchmark should cover Presigning and Signing phases.
The number of participants should be the max number of 2*malicious parties + 1

The measured parameters are:

End-to-end computation time (with/without latency) per participant
Total amount of data sent per participant
Computation time per participant (without send and receive)
Size of storage

The technique used to measure these factors is by participants simulation (described in #135 )

Resources & Additional Notes

Even though the scheme allows for robustness, changing the number of parties between the phases is not included in the scope of this issue.

Reference: "Mother of all Benchmark Issues" #135

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions