On Wed, 15 May 2024, David Pfitzner via curl-library wrote:
From testing, this change appears to be due to this commit: https://github.com/curl/curl/commit/db5c9f4f9e0779b49624752b135281a0717b277b
So just reverting this single commit makes it "good" again?
Perhaps it would be useful for a user of libcurl to be able to (somehow) control this tradeoff between rate-limiting accuracy and CPU usage?
Perhaps getting more data would be a first step. How big difference in rate-limit accuracy does this commit make in your case?
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
