← All episodes
Aharon BrodutchIlia Khait

Episode · Dec 26, 2022

Aharon Brodutch & Ilia Khait, Entangled Networks

Optical links to stitch small QPUs into one machine

Summary

Aharon Brodutch and Ilia Khait, co-founders of Entangled Networks, a company building an optical interconnect between QPUs are interviewed by Yuval Boger. Aharon, Ilia, and Yuval talk about the efforts required to scale up quantum processors, their optimizing compiler, building a distributed quantum computer, and much more.

Key takeaways

  • Entangled Networks is building an optical interconnect that links separate quantum processors together instead of trying to scale a single monolithic chip.
  • Their compiler has to decide how to split and route a circuit across multiple linked QPUs, treating the network link itself as a resource to optimize.
  • Photons are the natural carrier for entangling separate processors because light can travel between dilution refrigerators without the qubits themselves having to move.
  • Scaling by networking QPUs lets hardware vendors keep improving individual chips while the interconnect layer handles turning many small machines into one larger distributed computer.

Transcript

Yuval Boger: Hello, Aharon. Hello, Ilia. Thanks for joining me today.

Aharon Brodutch: Hi, thanks for having us.

Yuval: So who are you and what do you do?

Aharon: So, we're Entangled Networks, and we are solving the most important problem in quantum computing, and that is the problem of scaling up. At the end of the day, you need a large quantum computer to run things on, and the only way to scale up to really large sizes in a sustainable way is to take lots of small quantum computers, connect them together, and build a large quantum computer made up of many nodes.

We are building the enabling technology for that. That's a piece of hardware, a quantum interconnect that allows you to connect these quantum computers together into a network, but also the software that allows everything to function together. And what we've realized over the last two years is that people know very little about the software layer.

There has been a lot of work done on trying to improve the hardware, which is incredibly difficult, but very little work done on the software. We are able to show that you don't need the hardware to be extremely good as long as you have good enough software tools to use the resources in the best way, and this is where we really shine.

Just personally about us: I'm Aharon, I'm the CEO of Entangled Networks. My background is in quantum. I've been doing quantum since about 2007.

Ilia Khait: Ilia? Yeah. So I'm the CTO of Entangled Networks. My background is in condensed matter physics, with expertise in numerical algorithms, many-body systems, strongly correlated particles, things like that.

Yuval: So, let's dive into the first part of your answer, about the ability to scale. IBM says that they have a development roadmap, and they seem to be sticking by it. They have more and more qubits. Quantinuum is saying that they're increasing their quantum volume tenfold every year, I think. So couldn't we just wait until there are enough qubits?

Why do we need interconnects for smaller computers?

Aharon: So, if you look at IBM's roadmap, they're going to scale up to about 1,000 qubits before they start connecting devices together into a larger device. That's very clearly on their roadmap. And if you look at IonQ's roadmap, it's the same.

At some point, very clearly, you go into optical interconnects that allow you to go outside of your small quantum computer. If you look at Quantinuum, they're taking a slightly different approach, in that they're going to use shuttling. You're still going to have a distributed machine with lots of different small processors, but they're going to use shuttling to move ions from one side to the other. That can take you to a certain extent, but beyond a few thousand qubits, you are going to want to go optical.

And maybe one thing that you're seeing in terms of how technology is developing is that companies are doing two things. One, they're increasing the number of qubits, and two, they're increasing the capabilities of the gates, or the per-qubit capabilities of the device. As an example, IBM have an insane 127-qubit machine, which is an amazing engineering feat, but that is not their best-performing machine.

Their best-performing machine is a 27-qubit machine, and that's mostly because it's much harder to improve two-qubit gates on a larger device than on a smaller device.

Yuval: So how does the interconnect work, and does it work?

Ilia: So first of all, it works. Experiments in late 2019 showed a connection between two, let's call them distant, qubits.

By distant, I mean qubits that sit on two different devices. Maybe the rate was not super impressive; it was below 200 hertz. But what we show is that we can improve that rate, by using the methods that Aharon described earlier.

That means by better compilation and by very clever real-time policies, we can actually make that link work, and make algorithms perform.

Yuval: And regarding the first part of the question, how does it work?

Ilia: So basically, the most important piece is entanglement.

Hence our name, right? But generally speaking, what you need to have is a channel to exchange information, and that channel is entanglement between two qubits, a single qubit on each device. That allows you to perform a single operation, a single two-qubit operation if you wish, across the devices.

It's a single-use link, so once you use it, you need to produce another pair, another piece of entanglement, if you wish.

Yuval: Do you envision this being used primarily to interconnect pieces of the same computer? In your example, Aharon, you said IBM may have a 1,000-qubit chip one day, but then to scale up they would need to interconnect them.

Or do you see this more as a distributed supercomputer type of thing, meaning I have multiple quantum computers in different cities and I just want to network them together to get a larger number of effective qubits?

Aharon: So I think there are two questions that you asked there.

One is about interfacing different modalities, and the other one is about interfacing a large network. There is an added problem if your network is bigger, if it goes across distances, in that you need quantum repeaters in order to make the channel more reliable. So we're not looking at that for now, but certainly at some point we would like to have distributed computers.

If you're thinking over long distances, what you want is not speed, right? If you have a supercomputer, you don't want that supercomputer to be distributed around the world; you want it at one location. And it's the same for a quantum computer. But what a computer distributed over vast distances gives you is added security.

You can do things like delegated quantum computation, and things like that. And you can also exploit resources that you just don't have on hand in your one device. But this is much further into the future. If you're thinking of a network, first get that network to work on a small scale, right?

First get something to work in a room, and then you can start thinking about the next step. So that's about a quantum internet kind of world, and certainly that would be very interesting. The other one is about different modalities. Again, there is a huge technological opportunity there, but it is extremely difficult to interface even similar modalities with slight differences in the architecture.

For example, using two ion traps with different types of ions, you need to convert wavelengths. And if you're trying to interface an ion trap with a superconducting qubit, you need to go from microwave, which is where superconducting qubits work, to optical, which is where the ions work, and doing that is incredibly difficult.

So for now, the first challenge is getting just one distributed quantum computing system to work. It's a challenge, and it's a need for the industry. It's just hard to build a large quantum computer without this solution, and so everyone has to race very quickly to solve this problem.

But once you've solved it, you can start thinking about the next problem, which is how do we get a superconducting qubit, which works extremely fast, to interface with an ion qubit, which has an extremely long lifetime? And then you can exploit the advantages of these different architectures, in a way that's kind of similar to a computer that you have today, where different pieces serve different purposes.

Ilia: But unlike in classical computing, where you have standards, in quantum we're quite far from that at the moment.

Yuval: Today, a transpiler has to do a fair amount of work to optimize the circuit for a given hardware, for instance, to minimize the number of swap gates and so on.

If you have operations that happen on both sides of the entanglement link, and you mentioned that it might be slower, lower bandwidth, then you probably need a software layer that says, "Okay, how do I partition that circuit so that part of it runs on one computer and part on the other?" How is that happening?

Is that part of your offering?

Ilia: Right. So that is the main offering, or the main piece of the compiler: we want to reduce the number of inter-QPU, quantum processing unit, operations. But in order to facilitate that, we also better distribute the qubits in the first place.

So pieces of the quantum circuit, or pieces of the code, are distributed in a smart way to begin with, such that these small instances can run on different cores. But there is also a very important piece, which is what you do in real time.

But that is what happens after the compiler.

Aharon: So maybe on the compiler front, I can add a little bit. What we started off with is we said, from a theory perspective, we don't need a ton of entanglement in order to get a huge advantage from a multi-core processor.

So we looked at algorithms, and we saw that the number of times you'd have to exchange information is huge. And our reasoning was that this is probably a compilation problem. It's probably not working because the compilers are not built to solve this problem. So our first piece of software was a compiler that does this, so that we could start internally testing and understanding how many times you need to transmit information from one side to the other.

So we built a compiler, and as we were building it, we also tried to test it out on some other devices that are not distributed quantum computers, the things that exist out there. And we saw that we've actually hit on a nice way to do compilation that is independent of a distributed system, but relates very much to the connectivity constraints that you have on most architectures today.

So really, we have this incredibly nice tool. And just to understand how important compilation is, we're seeing up to a 90% decrease in the number of interconnect operations when we compare our compiler to some other commercial compilers out there that try to brute-force minimize the number of two-qubit gates.

And once you look at it as a distributed problem, you're also reducing the number of two-qubit gates. We're getting that extra advantage that I was mentioning earlier.

Yuval: You mentioned earlier IBM's 27-qubit and 100-or-so-qubit machines, but they have different gate fidelities, or a different two-qubit gate noise model.

Have you simulated the effect of scaling up? Could you, for instance, say that if you networked multiple of these 27-qubit chips, you would get something that's better than the 100-qubit chip?

Aharon: So that's a fantastic question. This is something we're doing right now. There are limitations to what you can simulate classically.

Right now we can do these kinds of estimates on smaller instances, where we can do a complete simulation of the architecture. We can say, what would happen if you took two 10-qubit machines and connected them together with certain specifications that we can get from IBM's website, or from Azure, or from AWS.

And we definitely see that the interconnect doesn't have to be extremely good. That being said, with superconducting architectures specifically, there are no good interconnects at the moment. So it's going to be a much harder challenge for the industry as a whole to connect superconducting machines together.

But IBM have promised that they're going to do it, and IBM have so far delivered on their promises. So I am optimistic that we'll see superconducting devices being connected together in the not-too-distant future.

Yuval: Tell me a bit about the company. Where are you located? How large is the company?

At what stage? How close are you to a working product?

Ilia: So the company consists of seven physicists. It was founded by me, Aharon, and Rafi. Rafi Gidron is a serial entrepreneur. One of his biggest claims to fame was Chromatis Networks, which was sold for about, what was it?

Aharon: 4.5 billion.

Ilia: Yeah, a lot of money, to Lucent. That was the first Israeli unicorn, I guess. Other than that, as I said, seven physicists here in Toronto, Canada.

Aharon: What else? We've existed for two years. We're funded by OurCrowd. We received the funding in May…

Ilia: 2021.

Yeah.

Yuval: How close are you to having a working product?

Ilia: That's a great question. As we pointed out in the beginning, there's no USB-style plug-and-play system in quantum, especially for interconnects. Therefore, our biggest challenge at the moment is to find the right partner, and to build that system specifically for their devices.

Having said that, we have a detailed blueprint for a prototype, and we're beginning to engage with partners to build it right now. So I'd say about a year from now we'll have our first actual prototype…

Aharon: …for demonstration. And that's on the hardware front. On the software side, like I said earlier, we have a compiler.

It works. We're not making it available to the public yet, but it works, and if anyone is interested in trying out multi-core algorithms, we're happy to discuss and show off the abilities…

Ilia: …there. And just to add some more meat on the compiler front:

As Aharon pointed out before, we do see a lot of improvement on monolithic devices as well. So you can test it without going to a multi-core architecture, which doesn't exist at the moment. So there are definitely advantages to using it today.

Yuval: And thus, the business model is to partner with a hardware vendor that makes quantum computers and say, "We have a better interconnect, and this is the best way for you, hardware vendor, to scale up your computer."

Is that correct?

Aharon: So our business model is to be the Mellanox of quantum computing, doing exactly what they did in classical computers: providing the hardware and the software for making supercomputers. We're doing the basic network infrastructure for a large quantum computer.

And so it's…

Ilia: …it's a critical component. And the effort is kind of parallel. On one hand, quantum vendors will improve their qubits, they'll improve their QPUs in general, while we improve our interconnect. So it's an exponential growth of overall improvement in quantum computational power.

Yuval: As we get close to the end of our conversation, I want to ask you about alternatives. You mentioned that IBM says beyond 1,000 qubits they're going to have to start using interconnects. What kind of interconnects are they thinking about, to the best of your knowledge, if they're not Entangled Networks interconnects?

Aharon: So that is an incredibly good question. IBM have superconducting qubits. They work in microwave, and there are two general options to go outside the fridge. Maybe before that: you can also do a multi-core architecture inside the fridge, which is easier.

Our software solutions are built to handle that, but you don't need our hardware, which is an optical interconnect, inside the fridge. And definitely IBM are looking into that, but that gets you to about 1,000 qubits. Going beyond that, you need to go outside the fridge; otherwise you need an insanely large fridge, which they're building. They're building it, but that's going to house a limited number of qubits.

So they have two options. One is the long-term viable option, which is what we're building, an optical interconnect. You convert from microwave into optical, and then you go through an optical fiber into a switch, and it's an optical network. We've been building these kinds of optical networks for many years.

It's a fairly simple device once you're out into optics. The other option is direct communication via microwaves, and that has been shown experimentally, where you have a superconducting coax cable, or a super-cold coax cable. It's at 15 millikelvin, and you transmit microwaves through it to get one device to talk to the other.

That is a much bulkier solution. Imagine these super-cold coax cables going between 1,000 different machines, each one holding 1,000 qubits, to get to a million. It might work as a short-term solution when you're connecting five fridges, but in the long term we see the only option as being optical.

Yuval: Excellent. How can people get in touch with you to learn more about your work?

Aharon: Through our website. We're getting a lot of interest through our website, and we make sure to answer every single request that we get. I think that's the easiest. But you can also email us: aharon, my first name, @entanglednetworks.com, or ilya@entanglednetworks.com.

Or Twitter, LinkedIn. The usual methods to get in touch with people.

Yuval: Excellent. Well, Ilia and Aharon, thank you so much for joining me today.

Aharon: Thank you.