Elon Musk Goes INSANE in Exclusive Interview.. 12/23/2022

Elon Musk Goes INSANE in Exclusive Interview.. 12/23/2022
In this full length interview from December, 2022 Elon Musk goes insane talking to ex Twitter employees and users.
Look it’s, the point I’m trying to make here is view count is already counted. Like it it’s already a thing that is happening. But view count, currently the issue is that it’s going to Google Cloud instead of the on-prem.
The view count is making a call to, to Google Cloud in batches at a rate that is towards the magnitude slower than what is needed to render it with the current pipe. Yes. That’s the actual issue. But if you then say, okay, look, we don’t care about it being real time because something like a, is being updated about every second or so.
But if we set up on your tweets Yes. On most people’s tweets. No, I’m just saying like the update frequency is it’s near real time. But the point I’m trying is view counts are already counted. They’re just being batched and being sent over a slow pipe to an analytics pro software on Google Cloud.
Yeah. It’s, it, whereas the likes are using the on-prem data. And but you could, it that’s like an arbitrary decision. It could be used the on-prem database as well. Yes. If it had not been an arbitrary decision to go off-prem to Google Cloud, then it, we, it would be trivial to add likes.
It would be considerably easier. It wouldn’t be, it wouldn’t be onerous to add views. If, especially if you’re not like, too precise about exactly how many views there were, if you like, let it be a little, let it float a little bit and you occasionally drop a view, count that. So it’s cuz like we’re not like trying to balance a bank book here then I think views actually like, should, would be relatively easy.
If views were in the same database as likes, yes. It would be easy. Yeah, that’s what I’m saying. Sure. And it should be it’s absurd that views are on a totally different database in Google Cloud instead of the on-prem system. That that’s a unnecessary complexity.
The Twitter stack right now is like basically combining the difficulties of three different worlds, which is running a complex real-time on-prem database that’s in three data centers and Atlanta one year in Oregon, and one in sa. And Sacramento is like possibly the worst place to have a data center cause it’s hot.
And then the summer, the it got so hot that the data center failed. Cause HVAC didn’t work. But then in addition to that, you’ve got also using aws. So using Amazon and using Google Cloud. So all three are acquired to operate Twitter fleets. Fleets uses aws. They built all the fleets in Aw.
Yeah I read the Google Docs for why too. Basically. For what? For why they put fleets in aws, basically. They couldn’t get enough provisioning for the internal data centers. Yeah. Like Sam Pilar was, has been helping out and like I think Sam was saying there was like some pretty nutty amount of data storage.
It actually analytics for app versions that don’t exist anymore. Yeah. I think it was like 15%, maybe 20%. It’s was literally logging data from apps that don’t exist. That’s what, this is okay, that’s wow. So anyway, there’s a lot of crazy stuff. 25, 20 5% of the CPUs are running the ads prediction model.

#elonmusk #america #innervision

Author: MuskMan Editor

Leave a Reply