> It's running on Instagram's #Cinder fork that includes a JIT, lazy-loaded modules, pre-compiled static modules, and a bunch of other interesting tweaks against vanilla Python 3.10.
So not entirely just python 3.1.
Backend of Meta Threads is built with Python 3.10
191–200 of 458 posts
Re: Backend of Meta Threads is built with Python 3.10
#192Would love to know more details about the rollout. Because it's adding well over a million new users each hour which is pretty staggering.
Meta has 3.8 billion monthly active users across its products. A few million new people is less than 0.1% of the total. It's entirely within expected variance.
I think they're looking at it from a an individual product perspective. % users of an entire company can be extremely different than % growth of a new product, within that company.
My naive assumption is that they have some neat simulated user/load system to help identify any scaling issues that might arise when launching a service, and the extreme % growth. That 3.8 billion was spread over 15 years.
Re: Backend of Meta Threads is built with Python 3.10
#193Earlier quoted context omitted.
No, but appealing to 'we' is. Not that 'we' in this case has much meaning, it actually could read 'you'.
What other pronoun do you want OP to use? "Can I ban..." - well, obviously not. "Can you ban..." who is "you" in that case?
> "Can I ban..." - well, obviously not
Of course he can. And he already does I assume, considering his other remarks in the comment. So including him in the 'we' does not really make sense ... if you consider it a question. Which it is not.
> "Can you ban..." who is "you" in that case?
That would be us dude, but not him as there is no reason to ask him, his position is clear.
So he is telling us what to do, dressed up as a question.
Re: Backend of Meta Threads is built with Python 3.10
#194> It's running on Instagram's #Cinder fork that includes a JIT, lazy-loaded modules, pre-compiled static modules, and a bunch of other interesting tweaks against vanilla Python 3.10. So not entirely just python 3.1.
I have ported code from Cinder to CPython . The fork has some optimizations that can be easily put in CPython and Facebook is open to port features. I’m not sure if Facebook wants to continually have a fork but CPython is open to have those features merged in if they make sense.
Re: Backend of Meta Threads is built with Python 3.10
#195Earlier quoted context omitted.
Interesting and lovely to hear they decided to use Django. What is your source, though?
It's a heavily modified internal fork of Django. Source: I work on our Python Language Foundation team.
What exactly do you do? This sounds like a JIT/Interpreter/Language dev job. Is this correct?
If so, do you have any recommendations or suggestions for someone getting their feet wet on this?
Re: Backend of Meta Threads is built with Python 3.10
#196For the “Python isn’t fast enough for production backend” crowd from the same company that brought you the largest social network built on PHP + MySQL.
Python is just fine for all the 100 users Threads will manage to acquire. :)
Re: Backend of Meta Threads is built with Python 3.10
#197Earlier quoted context omitted.
Is it really? Don't they work really slowly compared to most of the industry? I really get the impression that it's slow progress for things at FAANG.
Not really, especially Facebook (Meta) moves really fast. They have a slogan "Move fast, break things", okay not "Break things" anymore. But you get the gist, in my experience working at almost all of FAANG, Meta and Netflix move the fastest.
I think AWS must be the slowest of the bunch tbh. Too many meetings.
Re: Backend of Meta Threads is built with Python 3.10
#198Earlier quoted context omitted.
You mean the company that had to create their two PHP implementations and a translator to C++, to actually scale?
They ended up compiling PHP to assembly! Facebook is a company that will go to ridiculous lengths to avoid rewrites.
I know you're being hyperbolic, but during my time there, your impact was measured only on measurable things like performance gains but never on lines of code. So engineers would always go in the direction of whatever gets you the biggest win.
Sometimes that actually meant rewriting the thing from scratch, and other times that meant adding something else as a middleware to prevent touching the original thing.
For the most public success story, React was a complete rewrite of the thing before it, for example.
Re: Backend of Meta Threads is built with Python 3.10
#199For the “Python isn’t fast enough for production backend” crowd from the same company that brought you the largest social network built on PHP + MySQL.
For me, it does seem really strange since PHP (currently) is faster than Python and PHP wasn't fast enough for Facebook. But it's interesting to see how it'll play out.
Probably Python is deemed as more appealing to hipsters than good old PHP.
Re: Backend of Meta Threads is built with Python 3.10
#200There's definitely some overlap in the backends because https://www.threads.net/t/C is the first Instagram post but on Threads with the exact same amount of likes it has on Instagram yet https://www.threads.net/@kevin shows no threads.