-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: prepare v0.10.0 release #2198
Conversation
Did we want to switch to/enforce semver? (Not that this would be a point release.) |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2198 +/- ##
==========================================
- Coverage 95.41% 95.39% -0.03%
==========================================
Files 112 112
Lines 36447 36447
==========================================
- Hits 34777 34767 -10
- Misses 1670 1680 +10 ☔ View full report in Codecov by Sentry. |
Not sure I am following. Given that we are still See also https://semver.org/#how-should-i-deal-with-revisions-in-the-0yz-initial-development-phase. Related: as discussed elsewhere, I would like to release |
Failed Interop TestsQUIC Interop Runner, client vs. server neqo-latest as client
neqo-latest as server
All resultsSucceeded Interop TestsQUIC Interop Runner, client vs. server neqo-latest as client
neqo-latest as server
Unsupported Interop TestsQUIC Interop Runner, client vs. server neqo-latest as client
neqo-latest as server
|
Benchmark resultsPerformance differences relative to b516fe9. coalesce_acked_from_zero 1+1 entries: No change in performance detected.time: [99.237 ns 99.580 ns 99.924 ns] change: [-0.1955% +0.3028% +0.8458%] (p = 0.26 > 0.05) coalesce_acked_from_zero 3+1 entries: No change in performance detected.time: [117.70 ns 118.10 ns 118.53 ns] change: [-1.3111% +0.0444% +1.0187%] (p = 0.95 > 0.05) coalesce_acked_from_zero 10+1 entries: No change in performance detected.time: [116.94 ns 117.29 ns 117.74 ns] change: [-0.0761% +0.3806% +0.8728%] (p = 0.13 > 0.05) coalesce_acked_from_zero 1000+1 entries: No change in performance detected.time: [96.875 ns 97.047 ns 97.244 ns] change: [-0.6560% +0.0548% +0.8507%] (p = 0.89 > 0.05) RxStreamOrderer::inbound_frame(): Change within noise threshold.time: [112.05 ms 112.10 ms 112.16 ms] change: [+0.6822% +0.7624% +0.8403%] (p = 0.00 < 0.05) transfer/pacing-false/varying-seeds: No change in performance detected.time: [25.918 ms 26.973 ms 28.030 ms] change: [-4.9890% +0.0909% +5.4159%] (p = 0.97 > 0.05) transfer/pacing-true/varying-seeds: No change in performance detected.time: [34.506 ms 36.223 ms 37.909 ms] change: [-9.8457% -3.2970% +3.4744%] (p = 0.35 > 0.05) transfer/pacing-false/same-seed: No change in performance detected.time: [25.179 ms 25.979 ms 26.788 ms] change: [-7.1916% -3.2319% +0.9496%] (p = 0.15 > 0.05) transfer/pacing-true/same-seed: No change in performance detected.time: [39.875 ms 41.885 ms 43.942 ms] change: [-5.6432% +1.0900% +8.4766%] (p = 0.77 > 0.05) 1-conn/1-100mb-resp/mtu-1500 (aka. Download)/client: Change within noise threshold.time: [887.27 ms 895.81 ms 904.52 ms] thrpt: [110.56 MiB/s 111.63 MiB/s 112.71 MiB/s] change: time: [+0.7852% +2.1318% +3.5230%] (p = 0.00 < 0.05) thrpt: [-3.4031% -2.0873% -0.7790%] 1-conn/10_000-parallel-1b-resp/mtu-1500 (aka. RPS)/client: No change in performance detected.time: [323.89 ms 327.07 ms 330.28 ms] thrpt: [30.277 Kelem/s 30.575 Kelem/s 30.875 Kelem/s] change: time: [-0.0661% +1.4047% +2.9232%] (p = 0.07 > 0.05) thrpt: [-2.8402% -1.3853% +0.0661%] 1-conn/1-1b-resp/mtu-1500 (aka. HPS)/client: No change in performance detected.time: [33.611 ms 33.807 ms 34.022 ms] thrpt: [29.393 elem/s 29.580 elem/s 29.752 elem/s] change: time: [-0.8845% -0.1597% +0.6428%] (p = 0.69 > 0.05) thrpt: [-0.6387% +0.1599% +0.8924%] 1-conn/1-100mb-resp/mtu-65536 (aka. Download)/client: Change within noise threshold.time: [112.01 ms 112.36 ms 112.68 ms] thrpt: [887.46 MiB/s 889.98 MiB/s 892.78 MiB/s] change: time: [+0.8239% +1.2312% +1.6173%] (p = 0.00 < 0.05) thrpt: [-1.5916% -1.2162% -0.8172%] 1-conn/10_000-parallel-1b-resp/mtu-65536 (aka. RPS)/client: No change in performance detected.time: [317.12 ms 320.91 ms 324.66 ms] thrpt: [30.801 Kelem/s 31.161 Kelem/s 31.534 Kelem/s] change: time: [-0.0204% +1.5071% +3.1197%] (p = 0.06 > 0.05) thrpt: [-3.0253% -1.4847% +0.0204%] 1-conn/1-1b-resp/mtu-65536 (aka. HPS)/client: Change within noise threshold.time: [34.448 ms 34.662 ms 34.899 ms] thrpt: [28.654 elem/s 28.850 elem/s 29.029 elem/s] change: time: [+0.8907% +1.7000% +2.5915%] (p = 0.00 < 0.05) thrpt: [-2.5260% -1.6716% -0.8828%] Client/server transfer resultsTransfer of 33554432 bytes over loopback.
|
For the record:
|
I would like to get #2184 into Firefox.
Early integration looks promising.
While previously we would spend significant CPU time in allocating and de-allocating received

Datagram
s:https://share.firefox.dev/40bq7Ka
None of this is present with

v0.10.0
:https://share.firefox.dev/3NCMBfv