HomeVideos

The Craziest AI Pivot yet

Now Playing

The Craziest AI Pivot yet

Transcript

376 segments

0:00

If you weren't on the internet for the

0:01

last week, you may have missed it, but

0:03

Midjourney has decided to enter into the

0:06

medical arena. That's right. They're

0:08

throwing their hat into medicine. And

0:10

what they're effectively building is a

0:12

tube in which you go into and it

0:15

vibrates water and thus measuring the

0:17

vibrations is able to take a decently

0:20

accurate image of all the soft stuff

0:22

inside of your body. By the way, this

0:24

video very beautiful. Like I just even

0:26

me trying to even me trying to record

0:28

this YouTube video, I'm like watching

0:29

them like wow. They look so futuristic.

0:33

I've seen this this like on aliens. They

0:35

also released a blog going into the

0:36

details of how they plan on rolling this

0:39

out. What is their strategy? And a super

0:41

cool technical video actually breaking

0:43

down how this works, the data they had

0:46

to transfer and everything. Now, you're

0:47

probably thinking this is going to be me

0:49

making fun of an AI company. No, that's

0:51

not the plan of this video. No, I'm not

0:53

going to tell you about the efficacy of

0:55

the medical arena and whether

0:57

ultra-sonic scans are better than MRIs

0:59

or compete with MRIs or anything like

1:01

that, okay? Hey, if you're coming to me

1:02

for medical advice, you you messed up in

1:04

your life. I'm not even going to talk

1:06

about the fact that you probably are

1:07

going to have to get your MRI results

1:09

publicly on a Discord server. IN FACT,

1:11

I'M NOT EVEN GOING TO TALK ABOUT THE

1:13

FACT that they named it full body

1:14

ultra-sonic computational tomography,

1:17

okay? Or for short.

1:23

for short.

1:26

What the is going on here?

1:29

All right. for short. What I do

1:31

want to talk about are the numbers, the

1:33

actual data numbers, what they're

1:34

proposing because the technology that

1:36

they are proposing they're going to be

1:38

building over the next couple years is

1:40

literally space age technology alien

1:42

stuff. So, let's talk about it and why

1:44

honestly, it's the most it's the

1:46

craziest part of this entire pivot.

1:48

Midjourney going into medical, yeah,

1:50

that's kind of un- unexpected.

1:52

Midjourney saying what technology

1:53

they're going to build, nope. I don't

1:55

believe it for a second. But before we

1:57

begin, thank you to our sponsors.

2:01

Hey, do you like waiting? Yeah. Neither

2:04

do I. With Blacksmith, you get speed, 2x

2:07

faster hardware, 4x faster cash

2:09

downloads, and 40 times faster Docker

2:12

builds. So, stop waiting around. Use

2:14

their migration wizard to easily

2:16

transition your repos onto Blacksmith

2:18

today. Thank you, Blacksmith, for

2:19

sponsoring this video, and you, check

2:21

out the links down below. Hey, welcome

2:23

back. If you want to support the

2:24

channel, click the link in the

2:25

description. All right, so the blog

2:26

gives more details. So, it starts off by

2:28

saying, "Hey, Midjourney is going to

2:29

become a spa in which they're going to

2:31

be opening up the first one in San

2:32

Francisco in 2027, where they'll have

2:34

hot tubs, saunas, cold plunges, and of

2:37

course, a cozy rooms with pools of

2:39

golden light in which you can softly

2:40

scan your body."

2:42

Some weird. Also, that golden room, I

2:45

recognize that golden room, okay? That

2:46

is construct off of Halo. I've seen I've

2:48

actually I was birthed my I was birthed

2:50

in this room, okay? I know it quite

2:52

well. All right, so let's get into some

2:54

of the more technical parts about this.

2:56

Uh we first need to start off with their

2:58

just general goal. They want an

3:00

ambitious goal by 2031 to have a fleet

3:03

of over 50,000 scanners worldwide with a

3:06

scanning capacity of a billion scans a

3:08

month. So, that of course means if there

3:10

is 50K of these things and you have 30

3:13

days in a month, plus you have 24 hours

3:15

in a day, plus you have 60 minutes in a

3:18

hour, plus you have 60 seconds in a

3:21

minute, putting that all over 1 billion

3:24

means that at 50,000, you're going to

3:26

have to be scanning somebody every 129.6

3:31

seconds. So, already at that point,

3:33

that's just not going to happen, okay?

3:34

Every single machine which takes 60

3:37

seconds to scan somebody is going to

3:38

have to scan out, scan out, scan out.

3:43

So, but this is an important number to

3:44

keep in mind, because this is kind of

3:46

the basis of all the other numbers which

3:48

increasingly just get more and more

3:50

absurd. So, they're kind of their goal,

3:52

even if they were to double this instead

3:54

of having 50,000, they had 100,000,

3:57

still makes it so that you're scanning

3:58

somebody every approximately 4 minutes,

4:00

which just feels like that can't even be

4:04

done.

4:05

And that's 24 hours a day at any moment.

4:08

People are being scanned in every single

4:10

place continuously. Isn't it kind of

4:12

weird knowing that that's going to be

4:13

like the least crazy number that you

4:15

hear all day?

4:17

Like this entire video from here on out,

4:20

sorry, it's it's crazy land time. Okay,

4:22

everybody, we're going to get a little

4:24

bit more nuts now. In their technical

4:26

video breakdown on minute 3:32, right

4:29

here they say they generate 306

4:32

terabytes of raw data. Slightly before

4:35

that, they say they reconstruct all the

4:36

data across 21 servers. They claim that

4:40

each slice of the body takes about 40 GB

4:44

of data to move through the system. If

4:46

you're curious what a slice looks like,

4:47

it's this right here where you took the

4:49

body image and each one is this really

4:51

small thin slice of your body, so you

4:54

can slowly see every single bit of

4:57

information. They're claiming it's like

4:58

a half millimeter to 0.1 millimeter,

5:00

something like that. People are saying

5:02

maybe it's 2 millimeters per slice, but

5:04

it they're they're thin slices. Now,

5:06

this is where we're going to start

5:07

seeing some conflicting numbers start

5:09

happening. It also says that the system

5:11

captures about 17 GB per second. Their

5:15

goal is to capture several hundred

5:17

slices of your body. Now, if they would

5:18

have said a couple hundred, that'd have

5:19

been 200. If they would have said a few

5:21

hundred, I would assume that's 3 to 500.

5:23

Several hundred, that I mean, you can't

5:25

use several and not mean at least five.

5:27

Can we agree to that? Can we all agree

5:30

to that? So, it has to be many many of

5:32

slices of your body. So, I said all

5:34

those numbers off pretty fast. So, we're

5:36

actually going to start breaking it down

5:37

a little bit more. So, first off, they

5:39

did say they do a 17 GB of processing

5:42

per second. So, that puts us at

5:44

approximately 1 TB of information

5:47

processed for your 60-second scan, thus

5:51

leading to maybe about 500 images. There

5:54

are some estimates saying 300 images,

5:56

but let's just say it's about 500 you

5:58

know, images. That is going to be 1 to 2

6:00

GB per image. And that seems to make

6:02

sense because these are going to be

6:03

high-resolution images of your inside.

6:06

They need to be medical grade. You get

6:07

the idea. There are going to be some big

6:09

images. Now, here comes the point where

6:11

all the numbers are put together and

6:13

things are a little bit confusing. So,

6:15

first off, you have the machine that's

6:17

like the tube machine. Then you're going

6:18

to have your 21 computers way over here

6:21

that are going to be the 21 servers in

6:23

which can have that information. There's

6:25

going to be some sort of obvious

6:26

connection betwixt the two in which the

6:28

data from this machine needs to be

6:30

processed over here because you can't

6:32

just take the raw analog data shooting

6:35

out of these crazy little vibrating

6:37

sensors and then just make images out of

6:39

them, right? There has to be image

6:41

processing. Now, it says something along

6:43

the lines of 800 TB of raw data. Let's

6:46

just throw that number out cuz that

6:48

number is just it's just it's it's just

6:50

crazy, okay? Even if you had like the

6:52

world's fastest switch at 1.6 TB per

6:55

second, that's 66 minutes to get the raw

6:57

data over from here to here if you had

6:59

21 connections, each image being sent to

7:02

each individual 21 computers, that's 3

7:04

minutes of transfer time even on the

7:06

world's fastest network switching, all

7:09

local assuming no latency and absolutely

7:11

no frame dropping and absolutely 100%

7:13

utilization. So, what I think they

7:15

actually mean is that somewhere on this

7:17

machine the 800 TB, the 40 GB per image

7:21

somehow gets reduced and then sent

7:23

through the system to get crunched.

7:24

Maybe it's the 40 MB or GB per image

7:27

gets sent through the system to the 21

7:29

machines. You could imagine that each

7:31

machine receives maybe 40 GB at a time

7:34

to process that one image. And to me

7:36

that could potentially make sense. If

7:38

that were true, that would be about 20

7:40

TB worth of information, which is going

7:42

to take a decent amount of time to

7:44

transfer even if you have many

7:46

connections split up between every

7:47

single machine. And remember, we need to

7:50

be pumping out a scan every 129 seconds.

7:53

The transfer rate alone is going to eat

7:56

into that 129 seconds. Now, let's just

7:58

pretend that data transfer is zero and

8:00

we just simply think only about actual

8:04

frame production. If you remember the 1

8:06

billion row challenge in which you have

8:08

to calculate a median across a billion

8:11

rows, or maybe it's the mean, I can't

8:12

really even remember. Effectively, the

8:14

challenge comes down to memory mapping

8:16

12 GB file at once, doing a bunch of

8:19

integer parsing, and then boom,

8:20

calculating out the value you're looking

8:22

for. And some of the fastest times I've

8:24

seen are right around 1 and 1/2 seconds.

8:27

I'm sure there's some ones that are even

8:29

sub 1 second, but they all tend to be

8:31

right around in this range are the super

8:33

fast ones. Now, remember, the raw data

8:36

for the image is going to be 40 GB and I

8:39

have a a general assumption that you're

8:41

going to be doing a little bit more

8:42

processing and parsing on these raw data

8:46

images than you would be doing on the 1

8:48

billion row challenge. I'm just I you

8:50

know what, I'm just going to assume it's

8:52

slightly more complicated, but you do

8:54

have 21 servers, which means if I'm

8:56

being generous and you have 500 images,

8:59

but you have 21 servers, but they each

9:02

take 3 seconds, you're at about 71

9:05

seconds to be able to process

9:06

everything. So, that already is way too

9:10

much time. Okay, you got to be you got

9:12

to be processing so fast to be able to

9:14

keep up with this billion scans a month

9:16

demand across 50,000 machines. This is

9:18

going to be eating into a huge amount of

9:21

your time. But somehow, that's not even

9:23

the most absurd part, okay? If you have

9:26

1 billion scans per month,

9:29

and you have approximately 500 1 GB

9:32

images that you need to be sending up, I

9:35

d- I don't know what that extra letter

9:37

is there. That is going to be

9:38

approximately like 16 exabytes.

9:41

Obviously, we need to you know, there's

9:43

going to be some G zipping, things are

9:44

going to get a bit smaller. Let's just

9:46

say we can get down to four exabytes.

9:48

Today of under today's amount of

9:51

internet, this would represent

9:53

approximately somewhere between 12 and

9:55

1/2 to 25% of the total internet

9:58

transfer today. Just to transfer medical

10:03

images. Even if we were be using the

10:05

fastest Nvidia server rack costing $10

10:08

million plus 40 acres of storage plus a

10:10

gigawatt of power to be able to store

10:13

all of these images across a single year

10:15

of operating, 25% of the internet and

10:19

you're going to tell me you're going to

10:20

be able to do a billion of these scans

10:22

in a month. Like I think all the numbers

10:24

are wrong. You're not going to hit a

10:25

billion scans a month with 50,000

10:27

machines. Okay, you're going to need

10:28

like 500,000 machines. Second off, just

10:30

the pure sheer power that machine's

10:33

going to take locally is going to be

10:35

nuts. The amount of internet traffic

10:37

you're going to have to be able to

10:38

utilize is going to be just insane.

10:41

Every single day you're going to be

10:43

Netflix by itself. You you I mean four

10:46

exabytes is what Netflix does every day.

10:49

You will be Netflix just off of medical

10:51

images. Not to mention just the insane

10:53

amount of data warehouses you're going

10:55

to have to have plus the powers. You're

10:57

going to have to have a dedicated

10:58

nuclear reactor just to power the hard

11:02

drives. And look at this, none of these

11:04

calculations considered really like

11:06

speed of reading from RAM or speed to

11:09

writing to disk or what happens when you

11:11

have more memory and it needs to start

11:13

doing a little bit of flippity floppity

11:15

out of the RAM space onto hard drive

11:17

space. Like there's all sorts of real

11:19

world problems that would exist that

11:21

processing this amount of information is

11:23

not going to be done in 60 seconds or

11:25

less. It is not going to be gone in 60

11:28

seconds with Nicholas Cage, okay? It's

11:30

going to take many, many minutes. And I

11:32

assume you won't be able to run the

11:35

processing of information while stacking

11:37

up more. I I genuinely have no idea how

11:40

they're going to get there, but I do

11:41

want to say something that I think is

11:42

pretty neat. Is that Midjourney, the

11:45

image company,

11:46

is attempting to do more for medicine

11:49

than OpenAI and Anthropic and all the

11:52

other places currently that I've seen.

11:54

They're at least trying to It appears

11:57

that they're at least attempting to do

11:58

something because the whole kind of

12:00

stated mission is that if you can

12:01

measure yourself every single month, if

12:04

any of your organs or anything starts

12:06

changing shape or density, you'd be able

12:08

to identify it pretty quick, hopefully

12:10

leading to like a quicker, you know,

12:12

root cause analysis of some sort of

12:14

issue, thus potentially saving many

12:16

lives or extending lives. The obvious

12:19

The obviously hard part that I just

12:21

can't imagine is how can this be cheap?

12:23

How can you get a billion people? Like

12:24

how do you make technology that is

12:26

affordable to a billion people with the

12:28

numbers that we were talking about? Like

12:30

these numbers, to be able to set this

12:32

up, is going to be a hundred billion

12:34

dollars. You're going to cost as much as

12:36

an AI laboratory to be able to operate

12:38

just due to the sheer amount of volume

12:41

of data and the kind of equipment you

12:43

need to be able to process that much

12:45

load. Because they were saying that a

12:47

spa can hold like 10 units. So 50,000 is

12:50

going to be like 5,000 spas across the

12:53

world. And each one of these are going

12:54

to have to have a 10 million dollar

12:56

server farm in it. I'm not a math

12:58

magician and I don't think anyone can

13:00

multiply 5,000 by 10 million. Those

13:02

numbers are both way too big to multiply

13:04

together. Therefore, there's probably no

13:06

way anyone can afford that. Okay, hey,

13:08

we're all broke boys compared to that

13:09

number. But at the end of the day,

13:10

still,

13:11

Midjourney, appreciate you

13:14

doing something a little bit different.

13:15

Uh the numbers, I don't believe. Hey,

13:17

I'm glad to be proved wrong, but I'm

13:20

happy that you're doing this. The name

13:23

is the Primeagen.

13:26

Also, please don't let this be

13:27

vaporware. Please don't let this be the

13:28

greatest rug pull of all time, okay?

13:29

Come on. Don't let it happen. Don't let

13:31

it happen.

Interactive Summary

This video provides a critical technical breakdown of Midjourney's ambitious proposal to enter the medical field with a full-body ultrasonic scanning service. The creator examines the company's stated goal of establishing 50,000 scanning units worldwide to perform a billion scans per month, ultimately arguing that the logistics, data transfer requirements, and hardware infrastructure needed to support such a vision are implausible at the current scale.

Suggested questions

3 ready-made prompts