Re: [Capy review] On benchmarks

Steve Gerbino via Boost <[email protected]> Mon, 29 Jun 2026 13:35:49 +0000

Newsgroups	gmane.comp.lib.boost.devel
Message-ID	<bBshJt7zHbVPucfleYdS9V22xsyEZeb3Tk2IG8poZG6pS9cuX4_0g_pxNFUnSSolbUSRjgRdsG1np8n-TR_PzRUT5br0YDvABdroKON5Ijw=@gerbino.co>

On Monday, June 29th, 2026 at 2:35 PM, Ruben Perez via Boost <[email protected]> wrote:

> Hi all,
> 
> I've been reading the benchmarks page in Corosio
> (https://master.corosio.cpp.al/corosio/benchmark-report.html). The
> coverage seems quite impressive.
> 
> I've found a case ("socket bidirectional throughput") where Corosio
> seems 2 times slower than Asio
> (https://master.corosio.cpp.al/corosio/benchmark-report.html#_socket_io).
> Do we know what's the reason behind this? Would fixing it require
> significant architectural changes, or minor ones?

All these listed benchmarks are out-of-date. Our intent is to handle this in an automated fashion. The only way to see up-to-date is to run the suite locally at this time.
_______________________________________________
Boost mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.boost.org/mailman3/lists/boost.lists.boost.org/
Archived at: https://lists.boost.org/archives/list/[email protected]/message/QWH2INLNSEOUN2SPVKIVD37II5Z645QU/