gripleaf commented on PR #411: URL: https://github.com/apache/paimon-cpp/pull/411#issuecomment-6053648123
Benchmarked the latest revision, ce4c6d447dc84e396c2dcc4aa7916f726d363585, against the same integration baseline without this PR. Application code, dependencies, and configuration were unchanged. **Scenario:** An application resolves keys to row IDs, then fetches full rows from a Paimon table on HDFS. The fixed reference subset contains 100,000 keys and 42 columns. We tested single-key lookup, batched lookup, and paginated key-range scan with row-ID fetches. These are end-to-end application measurements using a native HDFS integration, including network and application overhead. | Workload | Concurrency | Keys/request or rows/page | Warm-up / measurement | |---|---:|---:|---:| | Lookup | 16 | 1 | 10 s / 60 s | | MultiLookup | 8 | 1,024 | 10 s / 60 s | | Range scan | 8 | 4,096 | 5 s / 30 s | Two warm runs per version; closed-loop load, identical reference keys, and 32 manifest scan threads. Lookup workloads sample the reference keys; scan covers their minimum-to-maximum key range. | Workload | AVG ms: baseline → PR | P99 ms: baseline → PR | Returned-row throughput | |---|---:|---:|---:| | Lookup | 923.44 → **28.37** | 2,193.62 → **55.22** | **33.16×** | | MultiLookup | 3,423.26 → **489.46** | 4,110.96 → **574.94** | **7.10×** | | Range scan | 5,438.25 → **2,426.60** | 7,489.55 → **3,718.29** | **2.24×** | Latency is per whole request/page, not per row. AVG and nearest-rank P99 pool raw samples across both runs. Baseline/PR sample counts: 2,067/67,568 (lookup), 280/1,952 (batched lookup), and 88/193 (scan); scan tail estimates are therefore limited. **Validation:** Reference-value checks passed (1,000 sampled lookup keys; all 100,000 keys through batched lookup and scan, plus duplicate-key cases). Benchmark requests had zero errors. The integration build passed 152 focused tests and the core suite with 2,334 passed / 100 skipped. AVG decreased by **96.9%, 85.7%, and 55.4%**, respectively. This measures the combined PR effect, not caching alone. Background errors overlapped candidate run 1; run 2 had none and showed similar performance, but shared-cluster interference cannot be ruled out. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
