remove the processor in aptos-core and reference to aptos-indexer-pro…

[larry-aptos]

Description

• Now all processors are migrated to Aptos Indexer Processors.

Test Plan

[bowenyang007]

Where do you reference the new processors?

[larry-aptos]

done

[github-actions]

✅ Forge suite compat success on aptos-node-v1.6.2 ==> 16cb7b2b47cb5b8a255bda30a577a66c2bd6e2b0

Compatibility test results for aptos-node-v1.6.2 ==> 16cb7b2b47cb5b8a255bda30a577a66c2bd6e2b0 (PR)
1. Check liveness of validators at old version: aptos-node-v1.6.2
compatibility::simple-validator-upgrade::liveness-check : committed: 3195 txn/s, latency: 6621 ms, (p50: 6600 ms, p90: 9900 ms, p99: 10800 ms), latency samples: 188520
2. Upgrading first Validator to new version: 16cb7b2b47cb5b8a255bda30a577a66c2bd6e2b0
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 1778 txn/s, latency: 15881 ms, (p50: 19300 ms, p90: 21900 ms, p99: 22600 ms), latency samples: 92480
3. Upgrading rest of first batch to new version: 16cb7b2b47cb5b8a255bda30a577a66c2bd6e2b0
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 1430 txn/s, latency: 16551 ms, (p50: 18900 ms, p90: 22500 ms, p99: 35700 ms), latency samples: 92960
4. upgrading second batch to new version: 16cb7b2b47cb5b8a255bda30a577a66c2bd6e2b0
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 3280 txn/s, latency: 9629 ms, (p50: 10100 ms, p90: 14000 ms, p99: 14200 ms), latency samples: 137760
5. check swarm health
Compatibility test for aptos-node-v1.6.2 ==> 16cb7b2b47cb5b8a255bda30a577a66c2bd6e2b0 passed
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite realistic_env_max_load success on 16cb7b2b47cb5b8a255bda30a577a66c2bd6e2b0

two traffics test: inner traffic : committed: 6333 txn/s, latency: 6179 ms, (p50: 6000 ms, p90: 7800 ms, p99: 12900 ms), latency samples: 2742460
two traffics test : committed: 100 txn/s, latency: 3013 ms, (p50: 3000 ms, p90: 3500 ms, p99: 3900 ms), latency samples: 1820
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.232, avg: 0.212", "QsPosToProposal: max: 0.194, avg: 0.156", "ConsensusProposalToOrdered: max: 0.652, avg: 0.612", "ConsensusOrderedToCommit: max: 0.547, avg: 0.510", "ConsensusProposalToCommit: max: 1.168, avg: 1.122"]
Max round gap was 1 [limit 4] at version 1271619. Max no progress secs was 3.979196 [limit 10] at version 1271619.
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite framework_upgrade success on aptos-node-v1.5.1 ==> 16cb7b2b47cb5b8a255bda30a577a66c2bd6e2b0

Compatibility test results for aptos-node-v1.5.1 ==> 16cb7b2b47cb5b8a255bda30a577a66c2bd6e2b0 (PR)
Upgrade the nodes to version: 16cb7b2b47cb5b8a255bda30a577a66c2bd6e2b0
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 4237 txn/s, latency: 7443 ms, (p50: 8100 ms, p90: 10500 ms, p99: 12000 ms), latency samples: 165260
5. check swarm health
Compatibility test for aptos-node-v1.5.1 ==> 16cb7b2b47cb5b8a255bda30a577a66c2bd6e2b0 passed
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking