Closed ajavadia closed 4 years ago
How do you feel about adding some applications benchmarks (e.g. VQE, operator estimation, hamiltonian simulation)? I can start a separate bug to discuss if you think that could be valuable.
@dongreenberg I definitely think that having some application benchmarks would be useful. In the first WIP version of the benchmark suite I had a vqe benchmark (based on terra's optimizers module which were removed in 0.7) but removed it by the time things finalized because the terra optimization module it depended on was removed.
@ajavadia - I started a PR with RB performance benchmark.
@ShellyGarion You run the benchmarks using the asv. I normally run things locally for testing with just asv dev
but you can also use asv run
especially if you want to test across the history. You can see current benchmark results here: http://169.61.88.206/
@ShellyGarion I'm not sure varying the seed affects things much from a performance point of view (you can try). The Clifford lengths are good. Maybe you can add 1Q RB as well.
@dongreenberg yes please add a couple applications too. Maybe one with a huge circuit, and one with many small circuits.
@mtreinish - the link for current benchmark results http://169.61.88.206/ does not work for me anymore
Yes, I implemented a more permanent hosting solution for the benchmark results since I left that comment last month. You can view the benchmark results here: https://qiskit.github.io/qiskit/
@ajavadia - I added several more parameters:
The RB performance benchmark is now reduced to the following parameters:
rb_pattern=[[[0]], [[0, 1]], [[0, 2], [1]]]
with the following default parameters:
length_vector = np.arange(1, 200, 4)
I think that this old issue could be closed @ajavadia @mtreinish Here is a link to RB performance test: https://github.com/Qiskit/qiskit/blob/master/test/benchmarks/randomized_benchmarking.py
Yep, this has been done since #306 and can be closed.
What is the expected behavior?
Let's add randomized benchmarking from Ignis as one of the benchmarks under
test/benchmarks
. It is helpful for tracking performance.