gnodet commented on PR #1938: URL: https://github.com/apache/maven-resolver/pull/1938#issuecomment-4829945948
_Claude Code on behalf of Guillaume Nodet_ Ran an independent benchmark with the reproducer project (814-module `server_subset`) to validate the changes. Each configuration was run 3 times to confirm consistency. ### Results **Maven 3.9.16 (baseline, classic resolver)** — stable across heap sizes: | Heap | Run 1 | Run 2 | Run 3 | Avg | |---|---|---|---|---| | 4g | 95.6s | 97.3s | 96.0s | **96.3s** | | 8g | 94.2s | 97.3s | 98.1s | **96.5s** | | 16g | 95.4s | 96.2s | 98.2s | **96.6s** | **3.10.0-SNAPSHOT (patched, auto mode selects path resolver)**: | Heap | Run 1 | Run 2 | Run 3 | Avg | Speedup | |---|---|---|---|---|---| | 4g | 74.9s | 73.0s | 73.2s | **73.7s** | **23%** | | 8g | 80.1s | 78.7s | 79.2s | **79.3s** | **18%** | | 16g | 83.7s | 83.4s | 87.8s | **85.0s** | **12%** | ### Observations - The patched path resolver is **12–23% faster** than the 3.9.16 classic resolver across all tested heap sizes. - The auto-selection heuristic correctly selects `path` for all 333 modules at every heap size tested (4g, 8g, 16g). - There is a minor slowdown with larger heaps for the path resolver (~11s between 4g and 16g), likely due to GC behavior with the parallel tree structure. The classic resolver is unaffected by heap size. -- 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]
