Yes, having an option would be helpful. But as I mentioned, the problem is not entirely in accuracy, but rather in the bias to take more bandwidth than expected. I guess when someone puts a rate limit, he/she expects a bias towards taking less bandwidth than the rate limit.
So, I think just simple bias correction towards taking less bandwidth will be helpful or maybe on option allowing to specify such bias. I am not sure if it is possible to improve rate limit accuracy without using more CPU cycles, but applying bias hopefully will not be that difficult. Thanks, Dmitry Karpov -----Original Message----- From: curl-library <[email protected]> On Behalf Of Daniel Stenberg via curl-library Sent: Thursday, October 30, 2025 3:12 PM To: Patrick Schlangen via curl-library <[email protected]> Cc: Daniel Stenberg <[email protected]> Subject: [EXTERNAL] Re: CPU usage since 8.7.1 On Thu, 30 Oct 2025, Patrick Schlangen via curl-library wrote: > It might not be the nicest API design, but would it be an idea to have > a curl option to chose between accurate and relaxed bandwidth > enforcement mode? If we end up in a situation where we can't satisfy everyone without an option, I think we can discuss that, sure. -- / daniel.haxx.se || https://rock-solid.curl.dev -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
