Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
Re: CPU usage since 8.7.1
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Stefan Eissing via curl-library <curl-library_at_lists.haxx.se>
Date: Tue, 28 Oct 2025 19:38:28 +0100
Hi Gleb,
> Am 28.10.2025 um 19:11 schrieb Gleb Smirnoff <glebius_at_glebi.us>:
>
> On Tue, Oct 28, 2025 at 05:32:27PM +0100, Daniel Stenberg wrote:
> D> On Tue, 28 Oct 2025, Gleb Smirnoff via curl-library wrote:
> D>
> D> > So here I am raising this question. What needs to be done to get CPU
> D> > savings of 8.6.0 level and how can we help here?
> D>
> D> As recall things, the change that introduced the new (current) behavior was
> D> done to enhance the accuracy of the rate limit logic, at the expense of
> D> CPU.
> D>
> D> The change was pushed for by someone who argued that the increased
> D> precision was valuable for them if I remember correctly.
> D>
> D> Can we find a way to have both ways and let the user select which? Maybe
> D> for example by maybe something as silly and simple as doing
> D> CURLOPT_MAX_RECV_SPEED_LARGE % 10000 and if that is non-zero, higher
> D> precision is wanted.
>
> I added Stefan to explicit Cc. Since he very recently added 24badd29f
> titled "limit-rate revisited" (of course this conlicted with out patch
> again), he definitely should have an opinion on how this can be solved.
I can have a look tomorrow at what we can do here. At what traffic are
you specifically interested in? HTTP/1.1 I assume?
Cheers,
Stefan
>
> --
> Gleb Smirnoff
Date: Tue, 28 Oct 2025 19:38:28 +0100
Hi Gleb,
> Am 28.10.2025 um 19:11 schrieb Gleb Smirnoff <glebius_at_glebi.us>:
>
> On Tue, Oct 28, 2025 at 05:32:27PM +0100, Daniel Stenberg wrote:
> D> On Tue, 28 Oct 2025, Gleb Smirnoff via curl-library wrote:
> D>
> D> > So here I am raising this question. What needs to be done to get CPU
> D> > savings of 8.6.0 level and how can we help here?
> D>
> D> As recall things, the change that introduced the new (current) behavior was
> D> done to enhance the accuracy of the rate limit logic, at the expense of
> D> CPU.
> D>
> D> The change was pushed for by someone who argued that the increased
> D> precision was valuable for them if I remember correctly.
> D>
> D> Can we find a way to have both ways and let the user select which? Maybe
> D> for example by maybe something as silly and simple as doing
> D> CURLOPT_MAX_RECV_SPEED_LARGE % 10000 and if that is non-zero, higher
> D> precision is wanted.
>
> I added Stefan to explicit Cc. Since he very recently added 24badd29f
> titled "limit-rate revisited" (of course this conlicted with out patch
> again), he definitely should have an opinion on how this can be solved.
I can have a look tomorrow at what we can do here. At what traffic are
you specifically interested in? HTTP/1.1 I assume?
Cheers,
Stefan
>
> --
> Gleb Smirnoff
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2025-10-28