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

Deploy Cardano transactions to testing-mainnet #1647

Closed
2 tasks done
jpraynaud opened this issue Apr 22, 2024 · 1 comment
Closed
2 tasks done

Deploy Cardano transactions to testing-mainnet #1647

jpraynaud opened this issue Apr 22, 2024 · 1 comment
Assignees
Labels
feature 🚀 New implemented feature

Comments

@jpraynaud
Copy link
Member

jpraynaud commented Apr 22, 2024

Why

We want to test the scaling performance of the Cardano transactions signature on testing-mainnet network in order to prepare the upcoming optimizations of the process

What

Activate the CardanoTransactions signed entity type on the testing-mainnet network and monitor the perfromances of import, signature and proof.

How

  • Activate the CardanoTransactions signed entity type on the network (environment variable of the network in GitHub)
  • Monitor the import the transactions (size, time, memory, cpu, ...)
@jpraynaud jpraynaud added the feature 🚀 New implemented feature label Apr 22, 2024
@jpraynaud jpraynaud self-assigned this May 2, 2024
@jpraynaud
Copy link
Member Author

jpraynaud commented May 13, 2024

Activation of the signature of the Cardano Transactions

(on the testing-mainnet network)

Aggregator:

  • Import of 90M transactions (10M blocks)
  • Generation of 675K block range roots
  • Import + generation done in 21h (less than 10min for the generation of block range roots)
  • Resources needed by the signer were low: 55MB RES and ~30-50% one core CPU
  • Database size of 26GB
  • No new open message created during the import (network stuck)

Signer:

  • Started import after the aggregator computed the first CardanoTransactions open message (~22h)
  • Import of 90M transactions (10M blocks)
  • Generation of 675K block range roots
  • Import + generation done in 21h (less than 10min for the generation of block range roots)
  • Resources needed by the signer were low: 55MB RES and ~30-50% one core CPU
  • Database size of 26GB (will be pruned so we expect ~1-2GB then)
  • No new open message signed during the import (network stuck)

The network is stuck for 2 days once the signature of the transactions is activated: we need to have a warm-up mode for the nodes in order to import the transactions without preventing the Mithril network to create new certificates.

Once the initial import is done, the overall signature process takes only few minutes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature 🚀 New implemented feature
Projects
None yet
Development

No branches or pull requests

1 participant