Add `asyncio_tcp` benchmark by kumaraditya303 · Pull Request #254 · python/pyperformance

I think that adding a new benchmark will consume the cost of running time for measuring.
Since we can not add every single benchmark for each dimension, each benchmark should cover a lot of dimensions of performance if possible.

If running time is a concern, we can restrict the set of benchmarks that are run by default. That is easily done in the manifest file. Then we can do longer runs whenever we feel comfortable with the extra time by passing the --benchmarks all (or maybe it is ""?) option to pyperformance.

In the long term, ideally we would have a solid set of workload-oriented ("macro") benchmarks that measure real-world performance (close enough, at least). This is what we would use to measure performance effectively and those results are what we would communicate to users. However, we still need the wide variety of feature-oriented ("micro") benchmarks, to help us avoid regressions and narrow down causes when we have regressions, as well as point to where possible improvements might be. See https://github.com/faster-cpython/ideas/wiki/All-About-Python-Benchmarking.

Currently, pretty much all of the pyperformance benchmarks are feature-oriented ("micro"). So we have plenty of work ahead of us. (Note that the pyston benchmarks are much closer to workload-oriented and we have been incorporating them into the faster-cpython results as much as possible.)