The GitHub Actions job "Pull Requests" on pekko.git/optimize-stream-boundary-batching has failed. Run started by GitHub user He-Pin (triggered by He-Pin).
Head commit for run: 33fb4b1e87b2c74dc5b51f9c3b5d35ff53395ba2 / 虎鸣 <[email protected]> perf: batch async boundary elements Motivation: Async stream islands send each element across the internal actor boundary as a separate boundary event, which adds per-element allocation and mailbox traffic. Modification: Batch elements produced during an interpreter run for internal stream boundaries and flush them when the interpreter parks. Keep external Reactive Streams subscribers on the per-element path, flush before completion, and clear pending batches on cancel/fail. Store initialized input and output boundaries in exact arrays and traverse them with indexed loops. Keep internal boundary subscriber calls concise and use the batch write index directly on the hot path. Result: Internal async boundary crossings allocate fewer boundary events and actor messages while preserving element order, demand, cancellation, failure, and supervision behavior. Tests: - rtk scalafmt --mode diff-ref=origin/main -- passed - rtk scalafmt --list --mode diff-ref=origin/main -- passed - rtk git diff --check -- passed - rtk sbt "stream / Compile / compile" "stream-tests / Test / testOnly org.apache.pekko.stream.FusingSpec org.apache.pekko.stream.scaladsl.PublisherSinkSpec" -- passed, 19 tests - rtk bash -lc 'sbt "bench-jmh/Jmh/run -wi 1 -i 3 -w 5s -r 5s -f 1 -prof gc .*AsyncBoundaryThroughputBenchmark.*" 2>&1 | tee /tmp/pekko-async-boundary-rename-index.log' -- passed - rtk qodercli --help -- passed, confirmed -p/--print, --output-format, --cwd, and --attachment - qodercli stdout review of /tmp/project-review.diff -- passed, no must-fix findings - Independent subAgent review of /tmp/project-review.diff -- passed, no must-fix findings References: None - internal stream boundary throughput optimization Report URL: https://github.com/apache/pekko/actions/runs/28713497916 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
