Buy commercial curl support from WolfSSL. 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
himself.
Re: performance tests
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Fabian Keil via curl-library <curl-library_at_lists.haxx.se>
Date: Thu, 9 Feb 2023 14:52:05 +0100
Daniel Stenberg <daniel_at_haxx.se> wrote on 2023-02-09 at 12:28:58:
> On Thu, 9 Feb 2023, Fabian Keil via curl-library wrote:
>
> > Long story short: I'd be interested to collaborate on creating curl
> > performance tests so I can leverage them to test Privoxy as well.
>
> I would imagine that we should start by making some infra to run "something"
> and then run that same "something" subsequently on fresh builds and output the
> results. This way we could detect slow-degrades (multi-days/weeks) and quick
> degrades (single commit). Also, some degradations have to be acceptable, for
> example if we add/change functionality etc.
>
> The complicated thing is of course that "performance" is a tricky beast and
> running things and timing them is difficult to get stable and avoiding false
> positives.
>
> Then over time extend what we run and monitor to cover more functionality.
Sounds good to me.
I still have to upstream my cts patch set for Privoxy but once
that's done I can look into adding new curl tests etc.
In the mean time I'll keep an eye on the curl commits to
see if anyone beats me to it ...
Fabian
Received on 2023-02-09
Date: Thu, 9 Feb 2023 14:52:05 +0100
Daniel Stenberg <daniel_at_haxx.se> wrote on 2023-02-09 at 12:28:58:
> On Thu, 9 Feb 2023, Fabian Keil via curl-library wrote:
>
> > Long story short: I'd be interested to collaborate on creating curl
> > performance tests so I can leverage them to test Privoxy as well.
>
> I would imagine that we should start by making some infra to run "something"
> and then run that same "something" subsequently on fresh builds and output the
> results. This way we could detect slow-degrades (multi-days/weeks) and quick
> degrades (single commit). Also, some degradations have to be acceptable, for
> example if we add/change functionality etc.
>
> The complicated thing is of course that "performance" is a tricky beast and
> running things and timing them is difficult to get stable and avoiding false
> positives.
>
> Then over time extend what we run and monitor to cover more functionality.
Sounds good to me.
I still have to upstream my cts patch set for Privoxy but once
that's done I can look into adding new curl tests etc.
In the mean time I'll keep an eye on the curl commits to
see if anyone beats me to it ...
Fabian
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
- application/pgp-signature attachment: OpenPGP digital signature