Release 2445 distribution
#2030
Comments
Cardano node warmupSelect the Mithril networkpre-release-previewexport NETWORK=preview release-preprodexport NETWORK=preprod release-mainnetexport NETWORK=mainnet Phase 0: Verify enough disk space is available in data diskAt least 50% of available space on data diskdf -h Phase 1: Warmup a temporary Cardano node from a Mithril snapshotaCreate temp dirrm -rf /home/curry/data/temp Download Mithril clientwget https://github.com/input-output-hk/mithril/releases/download/2442.0/mithril-2442.0-linux-x64.tar.gz Download latest snapshot./mithril-client cardano-db download latest Restore the Cardano nodedocker run -d --name cardano-node-warmup -v cardano-node-ipc:/ipc -v cardano-node-data:/data --mount type=bind,source="/home/curry/data/temp/db",target=/data/db/ -e NETWORK=${NETWORK} ghcr.io/intersectmbo/cardano-node:10.1.2 Phase 2: Switch Cardano database from the main node with the warmed-up oneCopy Cardano database to aggregatordocker stop cardano-node-warmup Cleanup directory (when node is back up)docker rm cardano-node-warmup |
Cardano transactions prover benchmarkNote run on GCP with
vs previous results
# Aggregator endpoint
export AGGREGATOR_ENDPOINT=https://aggregator.pre-release-preview.api.mithril.network/aggregator
# Transactions file to prove
export TRANSACTIONS_FILE=transactions-preview.txt
# Transactions proved per request range definition
export TRANSACTIONS_PER_REQUEST_MIN=0
export TRANSACTIONS_PER_REQUEST_MAX=50
export TRANSACTIONS_PER_REQUEST_STEP=10
# Apache benchmark total request sent per benchmark
export AB_TOTAL_REQUESTS=500
# Apache benchmark concurrency level range definition
export AB_CONCURRENCY_MIN=50
export AB_CONCURRENCY_MAX=50
export AB_CONCURRENCY_STEP=50
# Run the benchmark:
./benchmark-aggregator-prover.sh
MITHRIL AGGREGATOR PROVER ROUTE BENCHMARK
>> Aggregator endpoint: https://aggregator.pre-release-preview.api.mithril.network/aggregator
>> Aggregator route: /proof/cardano-transaction
>> Transactions file: transactions-preview.txt
>> Transactions available: [100]
>> Transactions per request range: [0 10 20 30 40 50]
>> AB concurrency range: [50]
>> AB total requests per run: [500]
>> AB total runs: 6
>> Output file: benchmark.csv
>> [#1/6] Running stress test with 500 requests with 1 transactions per request and 50 concurrency
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests
>>>> Success (53.93 requests/s)
>> [#2/6] Running stress test with 500 requests with 10 transactions per request and 50 concurrency
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests
>>>> Success (39.81 requests/s)
>> [#3/6] Running stress test with 500 requests with 20 transactions per request and 50 concurrency
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests
>>>> Success (25.17 requests/s)
>> [#4/6] Running stress test with 500 requests with 30 transactions per request and 50 concurrency
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests
>>>> Success (29.80 requests/s)
>> [#5/6] Running stress test with 500 requests with 40 transactions per request and 50 concurrency
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests
>>>> Success (23.59 requests/s)
>> [#6/6] Running stress test with 500 requests with 50 transactions per request and 50 concurrency
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Finished 500 requests
>>>> Success (21.11 requests/s)
>> Benchmark completed:
total_requests,concurrency,transactions/request,requests/s
500,50,1,53.93
500,50,10,39.81
500,50,20,25.17
500,50,30,29.80
500,50,40,23.59
500,50,50,21.11 |
Why
In order to deploy new features, improvements and bug fixes, we need to release a new distribution.
What
Create and release a new distribution
2445Important
10.1.2: Upgrade to Cardano10.1.1#2069pre-release-previewrelease-preprodrelease-mainnet10.1.2beaconfield in certificate #1958)Distribution +1:
Note
pre-release-previewrelease-preprodrelease-mainnetrelease-mainnetHow
Phase 1: Prepare distribution
crates.io(mithril-common,mithril-client)networks.jsonmust be updated following the runbookCHANGELOG.md(set the distribution version)10.1.2onpre-release-preview10.1.2onrelease-preprod10.1.2onrelease-mainnetPhase 2: Rollout pre-release distribution
pre-release-preview:10.1.2inpre-release-preview2445.0-prepre-release distribution on thepre-release-previewnetworkpre-release-previewpre-release-previewis working as expectednexthave been published on npm registry3signers running the new version (could be more if era change is tested) over at least2epochsPhase 3: Rollout release distribution
2445.0release distribution on thepre-release-previewnetworkpre-release-previewis working as expectedrelease-preprod:10.1.2inrelease-preprodrelease-mainnet:10.1.2inrelease-mainnet2445.0distributionrelease-mainnetrelease-mainnetis working as expectedrelease-preprodrelease-preprodis working as expectedlatesthave been published on npm registryCHANGELOG.md(updating the release date of the distribution)Phase 4: Activate features
>= 0.2.182(2437.1) is run by> 95%of the stake (within 2 weeks, or abort),release-mainnetrelease-mainnetdeployment in the CIrelease-mainnetis working as expectedrelease-mainnetThe text was updated successfully, but these errors were encountered: