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. |
||
|---|---|---|
| .. | ||
| core | ||
| BUILD | ||
| README.md | ||
| fuzztest_test.cc | ||
| grpc_fuzz_test.bzl | ||
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