daa5a23548
* Set self-adjusting deadline for connection writing In #16055 it appears that the simple 5s deadline doesn't work for large file writes. Now we can't - or at least shouldn't just set no deadline as go will happily let these connections block indefinitely. However, what seems reasonable is to set some minimum rate we expect for writing. This PR suggests the following algorithm: * Every write has a minimum timeout of 5s (adjustable at compile time.) * If there has been a previous write - then consider its previous deadline, add half of the minimum timeout + 2s per kb about to written. * If that new deadline is after the minimum timeout use that. Fix #16055 * Linearly increase timeout * Make PerWriteTimeout, PerWritePerKbTimeouts configurable Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: 6543 <6543@obermui.de> |
||
|---|---|---|
| .. | ||
| analyze | ||
| auth | ||
| avatar | ||
| base | ||
| cache | ||
| charset | ||
| context | ||
| convert | ||
| cron | ||
| csv | ||
| doctor | ||
| emoji | ||
| eventsource | ||
| generate | ||
| git | ||
| gitgraph | ||
| graceful | ||
| hcaptcha | ||
| highlight | ||
| httpcache | ||
| httplib | ||
| indexer | ||
| lfs | ||
| log | ||
| markup | ||
| matchlist | ||
| metrics | ||
| migrations | ||
| nosql | ||
| notification | ||
| options | ||
| password | ||
| pprof | ||
| private | ||
| process | ||
| public | ||
| queue | ||
| recaptcha | ||
| references | ||
| repofiles | ||
| repository | ||
| secret | ||
| session | ||
| setting | ||
| ssh | ||
| storage | ||
| structs | ||
| svg | ||
| sync | ||
| task | ||
| templates | ||
| test | ||
| timeutil | ||
| translation | ||
| typesniffer | ||
| upload | ||
| uri | ||
| user | ||
| util | ||
| validation | ||
| web | ||