Really, all the performance intensive parts are in various c++ aggregator and recommendation type services. But the webserver is Django, yes.
How heavily are type annotations and type checking used in the codebase?
Backend of Meta Threads is built with Python 3.10
91–100 of 458 posts
Re: Backend of Meta Threads is built with Python 3.10
#92Ironic that a post about Threads backend is hosted on twitter.
Is the person from Meta? Doesn’t appear so.
It’s still perfectly acceptable for Twitter users to discus other platforms on Twitter.
Re: Backend of Meta Threads is built with Python 3.10
#93Ironic that a post about Threads backend is hosted on twitter.
Is the person from Meta? Doesn’t appear so. It’s still perfectly acceptable for Twitter users to discus other platforms on Twitter.
He was and worked on, among other things, Python while there. He's a trustworthy source.
Re: Backend of Meta Threads is built with Python 3.10
#94Earlier quoted context omitted.
If you want real irony here, it's this: powering an app called Threads with Python that's got a global interpreter lock which makes threading hard. Get it? Threads, threading...? OK, I'll see myself out.
Meta does have their own higher-performance JIT-compiled implementation of Python, but I don't know if it still uses a global interpreter lock.
... wait, what? Did this morph out of HHVM? Any links on this?
Re: Backend of Meta Threads is built with Python 3.10
#95Re: Backend of Meta Threads is built with Python 3.10
#96Really, all the performance intensive parts are in various c++ aggregator and recommendation type services. But the webserver is Django, yes.
Interesting and lovely to hear they decided to use Django. What is your source, though?
Re: Backend of Meta Threads is built with Python 3.10
#97Earlier quoted context omitted.
A fair point that it's stupid to implement a mostly plain text publishing site that doesn't support linking to any of the text published there. Edit: Someone kindly pointed out that you can see the content in the browser without an account from following a direct link. (You just can't have the app installed or it will open that and drop you on the login page.) This makes me a lot happier with the product!
You can link to it, what are you talking about? An example fetched from a verge article -> https://www.threads.net/t/CuVaOg1PgU4/
They don't even have the dotcom?
Re: Backend of Meta Threads is built with Python 3.10
#98Would 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.
Re: Backend of Meta Threads is built with Python 3.10
#99Really, all the performance intensive parts are in various c++ aggregator and recommendation type services. But the webserver is Django, yes.
Interesting and lovely to hear they decided to use Django. What is your source, though?
How is Django now? I’m a long time python dev (data eng space) but new-ish to web dev. I started a Flask project 2 years ago and found it to be pretty full of footguns, mixed messaging on best practices for scalable apps, and the ecosystem feels overbloated with vapor ware extensions.
Is this just a Flask problem, or does Django have the same issues?
Re: Backend of Meta Threads is built with Python 3.10
#100Really, all the performance intensive parts are in various c++ aggregator and recommendation type services. But the webserver is Django, yes.
This would partially explain why it feels so slow. Some page refreshes are taking up to a couple of seconds.
It's probably hurried along python code and fairly simple horizontal scaling. Some population of individual instances are probably pegged, and random requests are frequently landing on their backlogged request queues.
This seems to have been rushed out the door to capture a unique market opportunity, and they'll clean up the engineering once they get engagement.