The problem is that it's not clear how useful those terabytes of information are. Ultrasound is very good for certain types of imaging, but the contrast mechanisms available are very limited - super high resolution images of uniform intensity aren't useful. An imaging method isn't useful if it doesn't help you discriminate what you want to see from what you don't. The reason MR is so useful is that it has so many contrasts available (T1, T2, proton density, flow speed, diffusion coefficient, diffusion direction, chemical composition, tissue elasticity, BOLD activation, and many other more esoteric ones). In an hour long scan, even with rapid acquisitions, you usually only get a few gigabytes of data, but that data has a LOT of information about your tissue - that's the reason the scanner keeps starting and stopping and making different noises, it's taking MANY different types of images with complementary information.

I once did IT support and I had a client who installed some malware that basically filled up his hard drive with nonsense. That was a lot of data really fast.

I think the point many commenters are making is that yes, lots of data IS necessary to do this scan effectively and quickly, it's not the only heuristic, and it's a bit misleading to compare it to the speed of an MRI given that this does not produce the same data as an MRI.

> That’s a lot of data really fast, so if you want this 3D scan of your body, yes, you do want as much data as fast as possible. 60 seconds sounds great compared to an MRI that’s going to take 15 minutes minimum & up to an hour or more.

This is deeply silly and nonsensical framing. You don't want "lots of data really fast", you want high-quality, diagnostically useful data. If the fastest way to generate that is via 15-minute MRIs, then that is vastly more ideal than a bullshit scan that takes seconds.