Re: [Capy/Corosio review] Benchmark results
Ruben Perez via Boost <[email protected]> Mon, 29 Jun 2026 12:54:02 +0200
| Newsgroups | gmane.comp.lib.boost.devel |
|---|---|
| Message-ID | <CACR-mdL5DT5ddVM1qBxJm9B_LqOy-baCx9AUvJ4YrJuMCEWQ0g@mail.gmail.com> |
On Mon, 29 Jun 2026 at 00:02, Marcelo Zimbres Silva via Boost <[email protected]> wrote: > > Hi, some months ago I started implementing new benchmarks for > Boost.Redis to compare it to the current state of other popular > clients. While underway with it Boost.Redis gained Corosio support, > something that has been announced by Ruben Perez in this mailing list > recently. Have you considered replicating your experiments on the cost of async abstractions [1], but for Capy/Corosio? I'd be really interested in the cost that tasks that complete immediately have. Note that I'm talking about tasks, rather than awaitables - so something like: capy::io_task<> queue_push(int value) { if (!full()) { container.push_back(value); co_return {}; } // wait for space } The reason why I'm asking this is because this is the kind of code that the "Application developers" user tier [2] has the ability to write, and hence the most abundant. Thanks, Ruben. [1] https://github.com/boostorg/redis/blob/develop/doc/on-the-costs-of-async-abstractions.md [2] https://isocpp.org/files/papers/P4172R1.pdf _______________________________________________ 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/BIZO2UVZFECE4RXMWTFY3AGFDGOL7KQF/