Skip to content
RESEARCH · QUANTUM CHEMISTRY / HYBRID COMPUTING

A quantum chemistry study cuts the cost of processing quantum measurements

Researchers use machine learning to reuse measurements from Google’s Willow processor. The gains concern one part of a hybrid workflow, not a demonstration of practical quantum advantage.

Published Source report Sources checked
Reading tools for text size, copying, printing and your reading list
My reading list
A path and landscaped grounds lead past Googleplex building 43.
Googleplex building 43 in Mountain View, photographed in July 2014. Archival company context; this is not the Willow laboratory or the reported chemistry experiment.Image: Googleplex building 43.jpg · Runner1928 · CC BY-SA 3.0Full image credit

A quantum computer can finish taking measurements and still leave an ordinary computer with a formidable amount of work. That less glamorous part of the calculation is the focus of a November 5 chemistry preprint from researchers at Harvard, Sandia National Laboratories and Google.

The team trains machine-learning models to reuse measurements from Google's Willow processor. In smaller tests using the same quantum data, the reported classical-computing cost falls by factors of 190 and 4,100 at eight and 16 qubits. Larger demonstrations reach a 40-qubit chemistry description. Those figures describe a particular hybrid method, not a quantum computer beating every classical alternative.[1]

The attraction is easy to understand: useful quantum computing needs an answer people can actually obtain. Measuring the processor is only one part of that job. A chemistry calculation also needs an appropriate starting description, a way to process measurements, a test of the resulting answer and an account of the resources spent along the way.

Reusing information instead of repeatedly unpacking it

Imagine receiving a large collection of observations and needing to answer thousands of related questions about it. One approach is to return to the original collection for every question. Another is to do more work up front, creating a compact model that can answer the particular questions you expect to ask.

The second approach can save time, but only if the model preserves what matters. A fast answer to the wrong question is not an improvement. Nor is a model that reproduces random fluctuations in its training examples instead of the underlying pattern.

That is a useful way to understand the engineering choice here. It also explains why the relevant comparison must include the cost of creating the model. Counting only its quick responses after training would hide part of the bill.

The comparison counts training-label generation, model training and trial-wavefunction evaluations: repeated mathematical queries used in the calculation. Unchanged propagation work elsewhere in the calculation is excluded. Conventional processing cost is extrapolated from a measured block, rather than a complete timed run. At larger sizes the authors cannot complete a direct benchmark. These are classical computational-cost comparisons, not measured end-to-end elapsed-time speedups. The authors use noisy hardware measurements and error-mitigation techniques; they do not report a fully fault-tolerant chemistry computation.[1]

What a large speedup can, and cannot, tell you

Consider an illustrative workflow, unrelated to the measured timings in this experiment. Suppose processing accounts for nine hours of a ten-hour job, while preparing and collecting its input takes one hour. Making processing 100 times faster reduces the total to 1.09 hours. The overall speedup is about 9.2 times, not 100.

Now suppose input collection takes nine hours and processing takes one. The same 100-fold processing improvement reduces a ten-hour job to 9.01 hours. The total improvement is only about 1.11 times.

Nothing about those examples diminishes a genuine software improvement. They show why knowing which part improved changes the meaning of the headline number. The formula is simply the unchanged work plus the accelerated work divided by its speedup.

The corresponding question for a quantum chemistry result is not just whether one stage became cheaper. It is whether the complete route to an answer is competitive at the required accuracy, including work done before the quantum processor runs. Readers should ask for that accounting before translating an impressive factor into a claim about useful advantage.

The starting-information catch

For the iron–sulfur demonstration, the researchers assume access to an accurate wavefunction and fit shallow circuits classically. The 40-qubit chemistry model is implemented as two independent 21-qubit circuits, including auxiliary qubits, using 42 . Its ground-state test uses hardware data, but its high-spin counterpart uses simulated data. Their combined energy-gap result therefore is not wholly hardware-measured.[1]

This makes the experiment informative about a component of the workflow, while leaving a broader challenge open. A method that works when supplied with a good starting description still needs a practical way to obtain that description for the harder problems researchers ultimately want to solve.

It is the difference between testing an improved stage of a scientific instrument and establishing the performance of the entire instrument. Both are worthwhile results. They answer different questions, and the distinction should survive the trip from the technical paper into a headline.

For readers following quantum computing, the useful takeaway is that progress can come from the ordinary computer working alongside the unusual one. More qubits are not the only lever. The next convincing step would pair efficient measurement processing with a practical preparation method and a complete, matched comparison against strong classical approaches.

The study offers a concrete reason to watch that interface. It does not yet justify declaring the whole chemistry problem solved.

Keep your reading trail

Evidence & context

2 linked sources

November 5 preprint, v1. Hardware data plus classical processing; measured-block cost extrapolation and simulated high-spin comparison are explicit. No practical advantage claimed.

How to read the evidence and dates

An announcement records what an organization stated. An experiment reports an observation. A simulation or resource estimate depends on its assumptions. QubitWire’s analysis connects these sources; the labels are not quality scores.

Published is the article’s first QubitWire publication. Updated marks a substantive content change. Sources checked records a review of the underlying evidence. An older paper can support a new explanation, and another press release about the same work is not independent replication.

QubitWire take

A stage-specific reduction in computing cost matters, but only complete resource accounting can establish practical advantage.

Sources

  1. Machine learning quantum data to accelerate quantum Monte Carlo

    Tong Jiang and colleagues, November 5, 2026 preprint. Figure 2, Figures 3–4, Supplement S3.4 and conclusion. Not peer-reviewed.

  2. Preprint abstract and submission history

    v1 submitted November 5, 2026; no subsequent version listed at source check.

Keep up with these topics

Explore the subjects covered in this story.

READ NEXT

Continue exploring

All Research stories
  1. Error correction / Research explained

    The quantum hardware did not change. Its error model did.

    A Riverlane preprint reports a better reading of existing error-correction data. Its measured-data result must not be confused with a larger simulation result.

    Published · Source report · Sources checked · About 4 min read
  2. Quantum software / Access explained

    Britain’s quantum programme is tackling the gap between a login and a useful calculation

    An NQCC agreement will give UK organisations access to Phasecraft software. The first cohort is planned for spring 2027; useful results still have to be demonstrated.

    Published · Source report · Sources checked · About 4 min read