Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MACI benchmarks #1081

Closed
1 of 7 tasks
ctrlc03 opened this issue Jan 22, 2024 · 1 comment
Closed
1 of 7 tasks

MACI benchmarks #1081

ctrlc03 opened this issue Jan 22, 2024 · 1 comment

Comments

@ctrlc03
Copy link
Collaborator

ctrlc03 commented Jan 22, 2024

Prerequisites

  • I checked to make sure that this request has not already been filed

Motivation

As a user and developers I want to know how much time and cost it takes to use MACI. I should be aware of the efficiency and costs (both time and gas cots) that I could incur on when using MACI (primary tasks - deployment, voting, proving).

Details

We have examples on how to write benchmarks

Is this for all packages? No, benchmarks for main tasks

  • contract deployment
  • signup
  • message posting
  • merging trees (incrementally larger number of users)
  • submitting proofs (incrementally larger batches & number of batches)

Implement benchmarks for the following:

  • contracts
    • Contract deployments costs
    • Contract usage costs per function
    • Coordinator costs for merging signups and messages
    • Coordinator costs for submitting proofs and commitments
  • proof generation
    • Generating proofs of message processing
    • Generating proofs of vote tallying

What is the final deliverable?

  • tools/code that anyone can run & tweak
  • GH action that can be run in CI: monitor how changes to code affect the benchmarks
  • documentation of these benchmarks (CSV format or similar?)
@samajammin
Copy link
Member

Closing in favor of #1194 #1195 #1196 #1197

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants