Jakub Dóka

@thomaseizinger sorry, I thought criterion was not needed since you mentioned I should just comment out the benchmark, making the criterion benchmark is kind of hard since it requires me...

Hey, @thomaseizinger, sorry for the delay, I was putting this off for a bit too long, here are my findings with criterion: ``` one_behavior_many_protocols_10000_10000 time: [371.18 ns 400.71 ns 432.65...

does memory transport deadlock on single-threaded mode?

welp, I can't find any reasonable difference now, I guess the protocol drops are not that significant when all the other code is run as well, so I was most...

Okay, @thomaseizinger, so, I had a bug in my benchmark, where it did the computation only in the first iteration, that explains why nothing made sense. Here are the results...

Here are the results I measured when backporting the benchmark to the old code (relative to the code in this PR). |behaviour count|poll count|protocols per behaviour|-|criterion timings |-|-|relative to optimized...

Benchmark results with applied modifications. Numbers are now more reasonable since both implementations need to do the initial protocol cloning. |behaviours|iters|protocols per behaviour|-|time-per-iter|-|-|relation to optimized version|-|verdict| |-|-----|--|---------|---------|---------|--------|--------|---------|--------------------------| |1|10000|10|7.6035 ns|7.7618 ns|7.9634...

Okay, do we need changelogs for this? Should I also squish the commits?

@thomaseizinger, sorry for the delay I made the changes

@thomaseizinger How can I troubleshoot the workflows? I focused on fixing one and now I cant find the other one. Is there an easy way to run them locally?