My understanding is that when running the QAOA implementation in aqua, the only timing information you can retrieve is the total wall-clock time, which is returned as the value of the key eval_time in the results dictionary. My understanding is that eval_time consists of the sum of the varying time in the queue, the classical optimization process involving updating the gammas and betas, the actual time it took to run the quantum circuits, etc. It would be great if a breakdown of eval_time was available. This would allow one to look into what parts of the overall application/algorithm it would be most worthwhile to look into to try to speed up.
What is the expected enhancement?
My understanding is that when running the QAOA implementation in aqua, the only timing information you can retrieve is the total wall-clock time, which is returned as the value of the key
eval_time
in the results dictionary. My understanding is thateval_time
consists of the sum of the varying time in the queue, the classical optimization process involving updating the gammas and betas, the actual time it took to run the quantum circuits, etc. It would be great if a breakdown ofeval_time
was available. This would allow one to look into what parts of the overall application/algorithm it would be most worthwhile to look into to try to speed up.