Skip to content

[true-async] bump base image to v0.7.0-rc.6 (restore HTTP/1+H2 perf)#776

Closed
EdmondDantes wants to merge 1 commit into
MDA2AV:mainfrom
true-async:h3-arena-rc6
Closed

[true-async] bump base image to v0.7.0-rc.6 (restore HTTP/1+H2 perf)#776
EdmondDantes wants to merge 1 commit into
MDA2AV:mainfrom
true-async:h3-arena-rc6

Conversation

@EdmondDantes
Copy link
Copy Markdown
Contributor

What

Bumps frameworks/true-async-server base image 0.7.0-rc.40.7.0-rc.6-php8.6.

Why

rc.6 reverts the experimental 1ms reactor-poll throttle back to the original CLOCK_MONOTONIC_COARSE jiffy (~10ms). The fine 1ms tick (introduced for an H3 PTO fix) regressed HTTP/1 (pipelined/baseline) and HTTP/2, which benefit from coarse batching (fewer reactor polls = fewer syscalls = more throughput). This restores H1/H2 to their prior numbers.

The H3 stream-credit fix stays in (server v0.7.1 — ngtcp2_conn_extend_max_streams_bidi on stream close, the thing that took baseline-h3/static-h3 c=64 from ~1277 req/s back to normal).

Supersedes #775 (rc.5 used an adaptive throttle that shifted the regression onto h2c at scale — rejected).

Image

trueasync/php-true-async:0.7.0-rc.6-php8.6 (on Docker Hub, php 8.6).

rc.6 reverts the experimental 1ms reactor-poll throttle back to the original CLOCK_MONOTONIC_COARSE jiffy (~10ms), which is what HTTP/1 (pipelined/baseline) and HTTP/2 want for batching. The H3 stream-credit fix (ngtcp2_conn_extend_max_streams_bidi) stays in (server v0.7.1). Supersedes MDA2AV#775 (rc.5 adaptive throttle regressed h2c at scale).
@EdmondDantes EdmondDantes deleted the h3-arena-rc6 branch June 1, 2026 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant