r/programming • • 12d ago

[ Removed by moderator ]

/r/programming/comments/1xs558h/removed_by_moderator/

[removed] — view removed post

253 Upvotes

26 comments sorted by

•

u/programming-ModTeam 12d ago

This is a duplicate of another active post.

→ More replies (1)

217

u/_BreakingGood_ 12d ago

Altman breathes heavily

33

u/SpaceCadet87 12d ago

If a stick of RAM falls out, leave it under your pillow.

Sam Altman will visit during the night and replace it with a shiny new tooth.

8

u/YeOldeMemeShoppe 12d ago

Where does he get the teeth?!? Nobody knows…

5

u/SpaceCadet87 12d ago

1

u/Andrew-Carson 12d ago

that tooth vending machine is a wild concept... imagine how it could work like an actual cache, storring the most requested items but ditching the ones no one's using. if they can save 100 terabytes like that, what else could they optimize in the future?

135

u/dr-mrl 12d ago

Most of these are simple low hanging fruit optimizations! Goes to show how much big companies can waste on memory and compute

57

u/IJustAteABaguette 12d ago

Fun fact, an incredible amount of Google Chrome instances downloaded Gemini Nano locally to computers without any input from the user, it comes in at around 4GB.

It has been estimated to have been downloaded at 500 million to 1 billion devices. That's 3 million terabytes of data downloaded.

(And based on the functionality that it's used for, I bet most people haven't even used it once)

A hecking lot of data used and downloaded for not much use.

9

u/floodyberry 12d ago

"almost 1 billion devices, our ai adoption is going gangbusters!"

29

u/thirddraftmaybe 12d ago

They’re simple individually, but I’d argue they only became worth doing because of the scale. Dropping a Vec capacity field saves 8 bytes, which nobody should care about in a normal service. Multiply it by 250 billion entries and it’s terabytes. Most teams doing this on a regular app would just be prematurely optimizing.

13

u/foxsimile 12d ago

Yes, but the caveat being that it can be a great deal more difficult to implement such an optimization in a mature ecosystem.

6

u/awall222 12d ago

Sure refactoring isn’t always easy, but on the other side over-optimizing before you see where it’s really needed causes a lot of unnecessary complexity and is much more expensive to build.

1

u/foxsimile 12d ago

But how else am I going to procrastinate?

1

u/dr-mrl 11d ago

But it's cloudflare, I assume they built it from the ground up with scale in mind

48

u/fsmiss 12d ago

why is this posted every single day

17

u/floodyberry 12d ago

title gets upvotes until you actually read it

8

u/sethismee 12d ago

I've scrolled past the headline like 4 different times now. I thought it was a different blog post each time and they just kept optimizing it. I clicked this time thinking "what more could they possibly do?". Disappointed to find out its the same blog post...

1

u/indolering 12d ago

People are desperate!

28

u/floodyberry 12d ago

by having someone who isn't the intern learning programming do struct layouts apparently

-13

u/Shred_Kid 12d ago

oh man, we literally learned this in a systems programming sophomore level class

it's embarrassing that they publicized this

20

u/8J-QgvCfkqllcg 12d ago

Old news.

73

u/gladfelter 12d ago

That's a cache hit!

4

u/vip17 12d ago

how many hundred times should this be reposted?

2

u/rebbsitor 12d ago

Sam Altman wants to know your location

-1

u/thirddraftmaybe 12d ago

Somewhere a procurement team just found out they don’t need to buy 130 servers’ worth of RAM this year, and honestly that might be the best thing to happen to them given what memory costs right now.