Hybrid Solver Timings
Using solvers other than the hybrid you can get a very detailed account of the timings of the problem such as qpu_access_time, qpu_programming_time, qpu_sampling_time, qpu_anneal_time_per_sample, qpu_readout_time_per_sample, total_post_processing_time, post_processing_overhead_time, etc. buy referencing sampleset.info["timing"].. This does not work using hybrid, but we would like to get more information about complex jobs besides QPU and real time. Like how much time was spent preprocess, how much time was spent postprocessing, how much CPU, QPU and QPU time was used.
Comments
Hello,
Unfortunately all of our hybrid solvers are proprietary, so we are unable to provide details about the requested information.
The following similar fields are provided:
qpu_access_time, charge_time, run_time
Descriptions of these info values can be found here:
https://docs.dwavesys.com/docs/latest/doc_leap_hybrid.html?highlight=charge_time#solver-timing
It is also possible to explore the dwave-hybrid framework:
https://docs.ocean.dwavesys.com/en/stable/docs_hybrid/intro/using.html
This is a way of utilizing the QPU in workflows that break down large problems.
This is not our Hybrid Solver Service, but might offer you the ability to create your own workflows with more control and customizability.
I hope this was helpful. Please let us know if you have any questions.
Please sign in to leave a comment.