fix(perf): TRex ASTFIPGenDist needs a [start,end] IP range#105
Conversation
…gle IP Run 28518413002 (post-#104) got TRex ASTF fully up (LRO fix worked, RPC serving, DUT tcp-echo bound) but every config failed at profile-build: Bad IP range "10.0.1.246" for parameter ip_range to function ASTFIPGenDist - Range should contain two IPs ASTFIPGenDist requires a 2-element [start, end] range even for a single host. Pass [ip, ip] for client/server/glob gens. Add a regression check (no TRex needed) asserting every ASTFIPGenDist ip_range is a list. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Synthetic Performance Results (run)Commit: ✅ synthetic UDP socket bound to 10.0.0.1:9000 (MAC: 02:00:00:00:00:01) Synthetic UDP Performance ResultsMeasures framework overhead: sync IPv4 Baseline
IPv6
IPv6 vs IPv4 Comparison (sync path)
IPv4 avg sync/async ratio: 1.0x, worst: 1.0x | IPv6 vs IPv4 worst ratio: 1.22x (OK)
|
Synthetic Performance Results — Graviton (run)Commit: ✅ synthetic UDP socket bound to 10.0.0.1:9000 (MAC: 02:00:00:00:00:01) Synthetic UDP Performance ResultsMeasures framework overhead: sync IPv4 Baseline
IPv6
IPv6 vs IPv4 Comparison (sync path)
IPv4 avg sync/async ratio: 0.9x, worst: 1.0x | IPv6 vs IPv4 worst ratio: 1.30x (OK)
|
[CI] Stage: DeployInfrastructure ready.
|
[CI] Stage: DeployInfrastructure ready.
|
[CI] Stage: SummaryAll tests PASSED. ARP seeding: kernel /proc/net/arp (automatic)
|
1 similar comment
[CI] Stage: SummaryAll tests PASSED. ARP seeding: kernel /proc/net/arp (automatic)
|
✅ Integration Tests Passed — Graviton (run)Branch: Test Results
Application Logs (last 20 lines)receiver-echo-server.log sender-echo-server.log sender-test-client.log |
✅ Integration Tests Passed (Run 28519883925)Branch: Test Results
Application Logs (last 20 lines)receiver-echo-server.log sender-echo-server.log sender-test-client.log receiver-test-client-iperf.log sender-test-client-iperf.log Full Application Logs (last 200 lines each)receiver-echo-server.logsender-echo-server.logsender-test-client.logreceiver-test-client-iperf.logsender-test-client-iperf.log
|
Follow-up to #104. That fix worked — run 28518413002 got TRex ASTF fully up (no LRO death, RPC serving, preflight passed) and
tcp-echobound on the real NIC. Next layer:TRex's
ASTFIPGenDistrequires a 2-element[start, end]range even for a single host. Every config failed at profile-build. Fix: pass[ip, ip]for the client/server/glob generators. Adds a regression check (grep-based, no TRex needed) asserting everyASTFIPGenDist(ip_range=...)is a list.py_compileclean, harness tests green. Merge → re-dispatch the TCP perf suite. This is the last known blocker before real DPDK-TCP numbers.🤖 Generated with Claude Code