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

[aip-43] Separate Concurrent Fungible Assets feature flag, for later release #11871

Merged
merged 1 commit into from
Feb 6, 2024

Conversation

igor-aptos
Copy link
Contributor

Description

Separating token v2 and fungible asset concurrent feature enabling:

Test Plan

Copy link

trunk-io bot commented Feb 2, 2024

@igor-aptos
Copy link
Contributor Author

Current dependencies on/for this PR:

This stack of pull requests is managed by Graphite.

Copy link

codecov bot commented Feb 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (793563f) 70.1% compared to head (50babba) 71.2%.
Report is 10 commits behind head on main.

❗ Current head 50babba differs from pull request most recent head 9fa8717. Consider uploading reports for the commit 9fa8717 to get more accurate results

Additional details and impacted files
@@             Coverage Diff             @@
##             main   #11871       +/-   ##
===========================================
+ Coverage    70.1%    71.2%     +1.0%     
===========================================
  Files        2182      794     -1388     
  Lines      414855   182772   -232083     
===========================================
- Hits       291207   130289   -160918     
+ Misses     123648    52483    -71165     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -287,13 +291,23 @@ module std::features {
/// Whether enable TokenV2 collection creation and Fungible Asset creation
/// to create higher throughput concurrent variants.
/// Lifetime: transient
const CONCURRENT_ASSETS: u64 = 37;
const CONCURRENT_TOKEN_V2: u64 = 37;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it okay to reuse the feature number 37 after deprecating CONCURRENT_ASSETS flag?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, it's safe to rename constants.

it is still the same flag (it was never enabled before), we just restrict it to gate less things (and so the rename)

Copy link
Contributor

@lightmark lightmark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

clean

@igor-aptos igor-aptos force-pushed the igor/separate_fungible_feature_flag branch from 50babba to 9fa8717 Compare February 5, 2024 23:50
@igor-aptos igor-aptos enabled auto-merge (squash) February 5, 2024 23:51

This comment has been minimized.

This comment has been minimized.

Copy link
Contributor

github-actions bot commented Feb 6, 2024

✅ Forge suite realistic_env_max_load success on 9fa871747e555de16b358392846b1873e94e5206

two traffics test: inner traffic : committed: 6977 txn/s, latency: 5477 ms, (p50: 5000 ms, p90: 7400 ms, p99: 12600 ms), latency samples: 3021380
two traffics test : committed: 100 txn/s, latency: 2173 ms, (p50: 2100 ms, p90: 2500 ms, p99: 3600 ms), latency samples: 1840
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.223, avg: 0.201", "QsPosToProposal: max: 0.148, avg: 0.139", "ConsensusProposalToOrdered: max: 0.593, avg: 0.552", "ConsensusOrderedToCommit: max: 0.471, avg: 0.448", "ConsensusProposalToCommit: max: 1.028, avg: 1.000"]
Max round gap was 1 [limit 4] at version 1424137. Max no progress secs was 6.719851 [limit 15] at version 1424137.
Test Ok

Copy link
Contributor

github-actions bot commented Feb 6, 2024

✅ Forge suite compat success on aptos-node-v1.8.3 ==> 9fa871747e555de16b358392846b1873e94e5206

Compatibility test results for aptos-node-v1.8.3 ==> 9fa871747e555de16b358392846b1873e94e5206 (PR)
1. Check liveness of validators at old version: aptos-node-v1.8.3
compatibility::simple-validator-upgrade::liveness-check : committed: 4822 txn/s, latency: 6482 ms, (p50: 6000 ms, p90: 10200 ms, p99: 17500 ms), latency samples: 183260
2. Upgrading first Validator to new version: 9fa871747e555de16b358392846b1873e94e5206
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 1758 txn/s, latency: 16696 ms, (p50: 19000 ms, p90: 22200 ms, p99: 22500 ms), latency samples: 91440
3. Upgrading rest of first batch to new version: 9fa871747e555de16b358392846b1873e94e5206
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 1789 txn/s, latency: 15812 ms, (p50: 19300 ms, p90: 21900 ms, p99: 22600 ms), latency samples: 93040
4. upgrading second batch to new version: 9fa871747e555de16b358392846b1873e94e5206
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 2939 txn/s, latency: 9939 ms, (p50: 9900 ms, p90: 18400 ms, p99: 20300 ms), latency samples: 126400
5. check swarm health
Compatibility test for aptos-node-v1.8.3 ==> 9fa871747e555de16b358392846b1873e94e5206 passed
Test Ok

@igor-aptos igor-aptos merged commit 8c4c16e into main Feb 6, 2024
80 of 84 checks passed
@igor-aptos igor-aptos deleted the igor/separate_fungible_feature_flag branch February 6, 2024 00:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants