Please sign in to comment.
perf: fix 1ms per async CopyAPI (regression since 42.2.5) (#1314)
The problem is SSL sockets use buffers for input, and `stream#available()` might easily return 0 even though the data is available in the downstream socket. The only viable WA is to perform `read` calls, however it might impact performance (e.g. for async copy operations). The resolution is to throttle read calls for copy api, and keep 1ms reads for replication api. fixes #1312
- Loading branch information...
Showing with 25 additions and 5 deletions.