ungate native memory operations

[igor-aptos]

Description

How Has This Been Tested?

Key Areas to Review

Type of Change

• New feature
• Bug fix
• Breaking change
• Performance improvement
• Refactoring
• Dependency update
• Documentation update
• Tests

Which Components or Systems Does This Change Impact?

• Validator Node
• Full Node (API, Indexer, etc.)
• Move/Aptos Virtual Machine
• Aptos Framework
• Aptos CLI/SDK
• Developer Infrastructure
• Move Compiler
• Other (specify)

Checklist

• I have read and followed the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I identified and added all stakeholders and component owners affected by this change as reviewers
• I tested both happy and unhappy path of the functionality
• I have made corresponding changes to the documentation

[trunk-io]

⏱️ 51m total CI duration on this PR

Job	Cumulative Duration	Recent Runs
execution-performance / single-node-performance	23m	🟩
rust-move-tests	13m	🟩
rust-move-tests	7m	🟥
rust-cargo-deny	4m	🟩 🟩
check-dynamic-deps	2m	🟩 🟩
general-lints	56s	🟩 🟩
semgrep/ci	47s	🟩 🟩
file_change_determinator	25s	🟩 🟩
permission-check	7s	🟩 🟩
permission-check	7s	🟩 🟩
check-branch-prefix	1s	🟩

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[igor-aptos]

• ungate native memory operations #15532 : 2 dependent PRs (#14917 , #15684 ) 👈 (View in Graphite)
• Optimizing vector::replace and compiler-v2 vector depenency fix  #15524
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

There appears to be a typo in the import statement - the trailing carg should be removed:

use aptos_transaction_generator_lib::entry_point_trait::PreBuiltPackages;

Spotted by Graphite Reviewer

Is this helpful? React 👍 or 👎 to let us know.

[github-actions]

✅ Forge suite realistic_env_max_load success on afc52013bbcbb0f0e546c68c645590b411308d0a

two traffics test: inner traffic : committed: 14665.80 txn/s, submitted: 14667.43 txn/s, expired: 1.63 txn/s, latency: 2702.53 ms, (p50: 2700 ms, p70: 2700, p90: 3000 ms, p99: 4200 ms), latency samples: 5576240
two traffics test : committed: 99.96 txn/s, latency: 1379.35 ms, (p50: 1300 ms, p70: 1400, p90: 1500 ms, p99: 1700 ms), latency samples: 1780
Latency breakdown for phase 0: ["MempoolToBlockCreation: max: 1.622, avg: 1.567", "ConsensusProposalToOrdered: max: 0.289, avg: 0.287", "ConsensusOrderedToCommit: max: 0.316, avg: 0.306", "ConsensusProposalToCommit: max: 0.603, avg: 0.593"]
Max non-epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 0.53s no progress at version 331 (avg 0.19s) [limit 15].
Max epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 0.58s no progress at version 2787344 (avg 0.58s) [limit 16].
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Validator CPU Profile
• Fullnode CPU Profile
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite compat success on 6593fb81261f25490ffddc2252a861c994234c2a ==> afc52013bbcbb0f0e546c68c645590b411308d0a

Compatibility test results for 6593fb81261f25490ffddc2252a861c994234c2a ==> afc52013bbcbb0f0e546c68c645590b411308d0a (PR)
1. Check liveness of validators at old version: 6593fb81261f25490ffddc2252a861c994234c2a
compatibility::simple-validator-upgrade::liveness-check : committed: 17601.32 txn/s, latency: 1940.61 ms, (p50: 2100 ms, p70: 2100, p90: 2200 ms, p99: 2400 ms), latency samples: 582900
2. Upgrading first Validator to new version: afc52013bbcbb0f0e546c68c645590b411308d0a
compatibility::simple-validator-upgrade::single-validator-upgrading : committed: 7877.07 txn/s, latency: 3852.43 ms, (p50: 4500 ms, p70: 4600, p90: 4800 ms, p99: 5000 ms), latency samples: 149740
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 7928.99 txn/s, latency: 4239.05 ms, (p50: 4600 ms, p70: 4700, p90: 5000 ms, p99: 5100 ms), latency samples: 264900
3. Upgrading rest of first batch to new version: afc52013bbcbb0f0e546c68c645590b411308d0a
compatibility::simple-validator-upgrade::half-validator-upgrading : committed: 7247.68 txn/s, latency: 4131.32 ms, (p50: 4800 ms, p70: 5000, p90: 5100 ms, p99: 5300 ms), latency samples: 136220
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 7251.68 txn/s, latency: 4580.29 ms, (p50: 4900 ms, p70: 5000, p90: 5100 ms, p99: 5200 ms), latency samples: 247440
4. upgrading second batch to new version: afc52013bbcbb0f0e546c68c645590b411308d0a
compatibility::simple-validator-upgrade::rest-validator-upgrading : committed: 12178.63 txn/s, latency: 2382.00 ms, (p50: 2700 ms, p70: 2800, p90: 3000 ms, p99: 3100 ms), latency samples: 218100
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 12326.98 txn/s, latency: 2652.49 ms, (p50: 2800 ms, p70: 3000, p90: 3000 ms, p99: 3300 ms), latency samples: 399980
5. check swarm health
Compatibility test for 6593fb81261f25490ffddc2252a861c994234c2a ==> afc52013bbcbb0f0e546c68c645590b411308d0a passed
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Validator CPU Profile
• Fullnode CPU Profile
• Test runner output
• Test run is land-blocking