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: relative performance
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Ben Greear via curl-library <curl-library_at_cool.haxx.se>
Date: Tue, 24 Aug 2021 08:27:39 -0700
On 8/24/21 8:20 AM, Daniel Stenberg via curl-library wrote:
> Hi all,
>
> For a long time I've wanted to get something done that allows us to compare curl's relative performance. Ideally something we can run every once in a while to
> compare that nothing major has turned sour without us being aware of it.
>
> A first step would be a tool we can run that measures "relative performance". Like doing N transfers of size X and measure how fast it can complete them.
> Running the same tool on the same host with the same server but built to use different libcurl versions should then not get noticably worse speeds over time.
> (Barring the difficulty of measuring network things when other programs are also running on the test host.)
>
> I'm not sure exactly how to do this, but I have a first shot at such a tool written and I figured we can create a new repository for this (curl/relative I'm
> thinking) and perhaps add more smaller tools for various tests as we advance. Then work out how to actually run them with different/current libcurls.
>
> Thoughts?
>
What is your network-under-test in this case?
And, if you want a network emulator (and don't want to mess with
netem), contact me off list, I'll give you free software licenses
for our product. Our rig can easily bundle a web server since a (virtual)
routed network too, so it should be a pretty complete test rig for this
case if you wish...
Thanks,
Ben
Date: Tue, 24 Aug 2021 08:27:39 -0700
On 8/24/21 8:20 AM, Daniel Stenberg via curl-library wrote:
> Hi all,
>
> For a long time I've wanted to get something done that allows us to compare curl's relative performance. Ideally something we can run every once in a while to
> compare that nothing major has turned sour without us being aware of it.
>
> A first step would be a tool we can run that measures "relative performance". Like doing N transfers of size X and measure how fast it can complete them.
> Running the same tool on the same host with the same server but built to use different libcurl versions should then not get noticably worse speeds over time.
> (Barring the difficulty of measuring network things when other programs are also running on the test host.)
>
> I'm not sure exactly how to do this, but I have a first shot at such a tool written and I figured we can create a new repository for this (curl/relative I'm
> thinking) and perhaps add more smaller tools for various tests as we advance. Then work out how to actually run them with different/current libcurls.
>
> Thoughts?
>
What is your network-under-test in this case?
And, if you want a network emulator (and don't want to mess with
netem), contact me off list, I'll give you free software licenses
for our product. Our rig can easily bundle a web server since a (virtual)
routed network too, so it should be a pretty complete test rig for this
case if you wish...
Thanks,
Ben
-- Ben Greear <greearb_at_candelatech.com> Candela Technologies Inc http://www.candelatech.com ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2021-08-24