Fix CPU spinning when curl_easy_send returns 0 bytes on SSL socket writes #6890
+12
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
Why ?
When uploading blobs to Azure Storage over HTTPS (SSL/TLS),
curl_easy_send()can returnCURLE_OKwith 0 bytes sent. This would lead to a retry without delay immediately, causing a tight CPU-spinning loop.What ?
Added a 10ms sleep when
curl_easy_send()returnsCURLE_OKwith 0 bytes sent to prevent rapid retries and allow the OS scheduler to run other threads.Test Plan: