Add objects test txns

[rtso]

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]

⏱️ 40m total CI duration on this PR

Slowest 15 Jobs	Cumulative Duration	Recent Runs
dispatch_event	10m	🟩
rust-doc-tests	5m	🟩
test-target-determinator	4m	🟩
execution-performance / test-target-determinator	4m	🟩
check	4m	🟩
rust-cargo-deny	4m	🟩 🟩
rust-move-tests	2m	🟩
fetch-last-released-docker-image-tag	2m	🟩
rust-move-tests	2m	🟩
check-dynamic-deps	2m	🟩 🟩
general-lints	1m	🟩 🟩
semgrep/ci	38s	🟩 🟩
file_change_determinator	18s	🟩 🟩
file_change_determinator	11s	🟩
execution-performance / single-node-performance	11s	🟩

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

[rtso]

• Add objects test txns #15203 👈
• main

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

Join @rtso and the rest of your teammates on Graphite

[github-actions]

✅ Forge suite realistic_env_max_load success on e05495422db608bce520f1a587c2d2b5de3279b2

two traffics test: inner traffic : committed: 14380.63 txn/s, latency: 2771.40 ms, (p50: 2700 ms, p70: 2700, p90: 3000 ms, p99: 4800 ms), latency samples: 5467880
two traffics test : committed: 99.95 txn/s, latency: 1559.80 ms, (p50: 1400 ms, p70: 1500, p90: 1600 ms, p99: 9100 ms), latency samples: 1800
Latency breakdown for phase 0: ["MempoolToBlockCreation: max: 1.965, avg: 1.561", "ConsensusProposalToOrdered: max: 0.335, avg: 0.295", "ConsensusOrderedToCommit: max: 0.367, avg: 0.354", "ConsensusProposalToCommit: max: 0.660, avg: 0.649"]
Max non-epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 0.67s no progress at version 2516785 (avg 0.20s) [limit 15].
Max epoch-change gap was: 0 rounds at version 0 (avg 0.00) [limit 4], 8.62s no progress at version 2516783 (avg 8.62s) [limit 15].
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 1086a5e00d773704731ab84fb4ed3538613b2250 ==> e05495422db608bce520f1a587c2d2b5de3279b2

Compatibility test results for 1086a5e00d773704731ab84fb4ed3538613b2250 ==> e05495422db608bce520f1a587c2d2b5de3279b2 (PR)
1. Check liveness of validators at old version: 1086a5e00d773704731ab84fb4ed3538613b2250
compatibility::simple-validator-upgrade::liveness-check : committed: 14636.42 txn/s, latency: 1954.16 ms, (p50: 1500 ms, p70: 1700, p90: 2000 ms, p99: 16900 ms), latency samples: 574580
2. Upgrading first Validator to new version: e05495422db608bce520f1a587c2d2b5de3279b2
compatibility::simple-validator-upgrade::single-validator-upgrading : committed: 7398.83 txn/s, latency: 3781.15 ms, (p50: 4200 ms, p70: 4500, p90: 4600 ms, p99: 4700 ms), latency samples: 136360
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 7601.39 txn/s, latency: 4240.24 ms, (p50: 4500 ms, p70: 4700, p90: 5500 ms, p99: 6100 ms), latency samples: 251640
3. Upgrading rest of first batch to new version: e05495422db608bce520f1a587c2d2b5de3279b2
compatibility::simple-validator-upgrade::half-validator-upgrading : committed: 6718.69 txn/s, latency: 4267.19 ms, (p50: 5000 ms, p70: 5200, p90: 5300 ms, p99: 5500 ms), latency samples: 121100
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 6319.17 txn/s, latency: 5175.66 ms, (p50: 5300 ms, p70: 5400, p90: 6700 ms, p99: 7100 ms), latency samples: 223940
4. upgrading second batch to new version: e05495422db608bce520f1a587c2d2b5de3279b2
compatibility::simple-validator-upgrade::rest-validator-upgrading : committed: 9736.24 txn/s, latency: 2874.54 ms, (p50: 2500 ms, p70: 2700, p90: 5100 ms, p99: 5400 ms), latency samples: 171440
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 9274.18 txn/s, latency: 3400.41 ms, (p50: 2700 ms, p70: 4400, p90: 5300 ms, p99: 6400 ms), latency samples: 310840
5. check swarm health
Compatibility test for 1086a5e00d773704731ab84fb4ed3538613b2250 ==> e05495422db608bce520f1a587c2d2b5de3279b2 passed
Test Ok

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