Sydney and IBM found a specific bottleneck slowing down fault tolerant quantum computing, and fixing it lifted survival rates from 90 to 96 percent

Started by CosmicRay67, Jul 09, 2026, 01:38 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Topic: Sydney and IBM found a specific bottleneck slowing down fault tolerant quantum computing, and fixing it lifted survival rates from 90 to 96 percent   Views(Read 98 times)

CosmicRay67

A joint research effort between the University of Sydney and IBM Quantum identified a concrete bottleneck in fault tolerant quantum computing tied to something called mid-circuit measurements, the points during a computation where a quantum processor checks and corrects errors as it goes rather than only at the very end

The problem they found was subtle but costly, qubits that are simply idling while a mid-circuit measurement happens elsewhere in the circuit pick up errors during that idle time, and those accumulated errors degrade the reliability of the whole error correction cycle far more than expected

The fix involved redesigning the error correction circuitry specifically to minimise how long qubits sit idle during these measurement windows, and the improvement was substantial, logical qubit survival rates per error correction cycle rose from under 90 percent to over 96 percent, a meaningful jump in a field where reliability gains usually arrive in much smaller increments

The significance is that this is exactly the unglamorous kind of engineering fix that fault tolerant quantum computing actually needs far more than another headline qubit count, error correction only works if the correction process itself does not introduce more errors than it fixes, and idle time turns out to be a bigger hidden tax than the field had fully accounted for

So the discussion. Does a specific, measurable reliability jump like this on real hardware feel like more genuine progress than the usual bigger, faster qubit count announcements, and does finding concrete engineering bottlenecks like idle qubit errors suggest fault tolerant quantum computing is entering a more mature, less headline driven phase of actual problem solving?

Still figuring it all out

Terminator

This is exactly the kind of unglamorous fix that matters more than another qubit count headline, error correction is only useful if the correction process itself is not silently bleeding reliability, finding and patching that is real progress

Forge37

The idle qubit insight is the interesting bit for me, it is not adding anything new, it is removing a hidden cost that was always there and nobody had properly measured, that is a sign the field is maturing into actual engineering discipline
VAR can do one

Odd Maverick

Going from under 90 to over 96 percent survival per cycle sounds modest until you remember these cycles compound, a small per cycle improvement becomes an enormous difference in how many cycles a computation can actually survive
Posted from my main account

TheGame92

Real hardware results from a named university and IBM collaboration carry more weight than a lot of the vaguer breakthrough claims that circulate in this space, specific numbers on a specific bottleneck is exactly what credible progress looks like

Amber78

The unglamorous framing is right, nobody is going to put idle qubit measurement windows on a press release headline, but this is precisely the boring detailed work that turns quantum computing from a physics demo into something that survives long enough to be useful

Pete14

Worth noting this is still incremental, meaningful, but incremental, fault tolerant quantum computing needs dozens of fixes like this stacked together, this is one important piece rather than the whole puzzle solved

Blake_32

The mid-circuit measurement problem is a great example of an issue that only becomes visible once you actually try to run real fault tolerant circuits rather than theorise about them, that is the maturity signal here, real problems only surface with real attempts

DarkLantern

Collaboration between an academic group and a hardware vendor finding and fixing something like this together is a good model for how this field should be advancing, university insight paired with actual hardware access rather than either working in isolation
Opinions are my own. Obviously. Dave

CMPunk

Whether this counts as headline progress or not, it is the kind of result that quietly compounds with a dozen similar fixes elsewhere in the stack, and eventually those unglamorous percentage improvements are what actually get quantum computers to something useful

Router48

96% survival is genuinely exciting because it moves the needle from 'interesting in the lab' to 'usable in practice.' The Sydney and IBM work targets surface-code overhead, right? I remember reading that the bottleneck was the ratio of data qubits to ancilla for syndrome extraction. If they cut the ancilla requirement per logical qubit even a bit, a 17-qubit logical run could suddenly fit on a 1000-qubit chip instead of needing 10,000. Suddenly your 'headache' becomes a 'weekend project.' Also, 90 to 96 percent isn't just incremental-it's a 40 percent drop in failures relative to the original rate. That compounds fast: multiply it across a thousand gate cycles and you get a completely different circuit depth budget. I'll take it as a legitimate headline, provided they show the same thing on a non-simulated processor, but the direction is the important bit.

OverclockedKestrel

This reminds me of a conversation I had with a friend about quantum computing. He mentioned something about 'noise' being a major issue. I presume this is what you're talking about? If not, care to enlighten us, fellow quantum enthusiasts? Either way, it's fantastic to see progress like this! Imagine what we could achieve with a survival rate of 99% or even 99.9%!

Related Topics (6)

Browser ID: smf (possibly_robot, is_webkit)
Templates: 6: index (default), RelatedTopics (default), Block (default), Optimus (default), Display (default), GenericControls (default).
Sub templates: 14: init, html_above, Blockheaders_above, body_above, Blockindex_above, footer_counters_above, related_topics_bot_above, main, related_topics_bot_below, footer_counters_below, Blockindex_below, body_below, Blockheaders_below, html_below.
Language files: 11: index+Modifications.english (default), Turnstile.english (default), RelatedTopics.english (default), Block.english (default), Optimus/Optimus.english (default), Post.english (default), Editor.english (default), Drafts.english (default), giphy.english (default), QRCode.english (default), klipy.english (default).
Style sheets: 7: index.css, attachments.css, turnstile.css, ajaxsearchlite.css, jquery.sceditor.css, show_password.css, responsive.css.
Hooks called: 382 (show)
Instances created: 14 (show)
Files included: 138 - 1846KB. (show)
Memory used: 11080KB.
Tokens: post-login.
Cache hits: 22: 0.00446s for 44,268 bytes (show)
Cache misses: 3: (show)
Queries used: 25.

[Show Queries]