grpc/fuzztest
Craig Tiller 7c59c09f43
[chttp2] Bound write sizes based on observed write performance (#34665)
Instead of fixing a target size for writes, try to adapt it a little to
observed bandwidth.

The initial algorithm tries to get large writes within 100-1000ms
maximum delay - this range probably wants to be tuned, but let's see.

The hope here is that on slow connections we can not back buffer so much
and so when we need to send a ping-ack it's possible without great
delay.
2023-10-12 16:48:55 -07:00
..
core [chttp2] Bound write sizes based on observed write performance (#34665) 2023-10-12 16:48:55 -07:00
BUILD [fuzzing] Roll forward dep on fuzztest (#32667) 2023-03-21 13:37:32 -07:00
README.md [fuzzing] Roll forward dep on fuzztest (#32667) 2023-03-21 13:37:32 -07:00
fuzztest_test.cc [fuzzing] Roll forward dep on fuzztest (#32667) 2023-03-21 13:37:32 -07:00
grpc_fuzz_test.bzl [fuzzing] Roll forward dep on fuzztest (#32667) 2023-03-21 13:37:32 -07:00

README.md

Tests that leverage fuzztest.

These require C++17 and so cannot be run with the standard build configurations.

To run these tests:

bazel run //fuzztest/path/to:test -c dbg --config fuzztest