-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
Maybe this is just The Passage of Time or different hardware, but I can't get the same results as shown in the bench shown in the read me,
I am running the benchmark on a AMD Ryzen 9 5900X
I even added Tokio to mine, but all (futures, tokio, catty) are within range of each other, I actually found for the bench a "giant" performance win, by making catty use either Future's or Tokio's async backend, but even then, while catty is consistently faster, it's only so by ~3-4ns,
Here's e.g. a comparison of Futures, on the futures executor, Tokio on both single and multi thread runtime, and catty on pollster, tokio (single and multi thread) and futures runtime
My complete benchmark results are as following
create/create-futures time: [94.775 ns 94.856 ns 94.941 ns]
create/create-tokio time: [93.758 ns 94.115 ns 94.492 ns]
create/create-catty time: [88.635 ns 88.674 ns 88.720 ns]
oneshot/oneshot-futures time: [99.772 ns 100.16 ns 100.49 ns]
oneshot/oneshot-tokio time: [105.58 ns 105.89 ns 106.09 ns]
oneshot/oneshot-tokio-mt time: [105.54 ns 105.96 ns 106.37 ns]
oneshot/oneshot-pollster-catty time: [185.05 ns 185.18 ns 185.36 ns]
oneshot/oneshot-futures-catty time: [97.085 ns 97.166 ns 97.261 ns]
oneshot/oneshot-tokio-catty time: [97.329 ns 97.475 ns 97.628 ns]
oneshot/oneshot-tokio-mt-catty time: [96.835 ns 97.082 ns 97.314 ns]
send/send-futures time: [97.753 ns 97.860 ns 97.982 ns]
send/send-tokio time: [96.641 ns 96.732 ns 96.841 ns]
send/send-catty time: [93.807 ns 93.859 ns 93.908 ns]
Metadata
Metadata
Assignees
Labels
No labels
