Tesla Engineers Visit Twitter Office to Review Code for Musk

Re:Tesla Engineers Visit Twitter Office to Review Code for Musk by rsynnott on Friday October 28, 2022 @05:45AM (#33369450)

I'm not sure how much telemetry Teslas actually send (do buyers really tolerate their absurdly expensive car reporting their every move back?), but in any case I would assume it all gets stored for bulk processing. Twitter's pretty different; when [insert celeb with 100m followers here] tweets, that tweet should show up for anyone who's looking at their profile, immediately. And the like and retweet counts should update for everyone looking at the tweet that just went out to 100m people (actually, it would be possible for Twitter to fudge this bit, but they don't seem to).

These might seem on the face of it similar problems, but really they're not at all. Ingesting lots of data is ~trivial; dealing with lots of data in realtime somewhat less so.

[ Parent | on HN ]

Re:Tesla Engineers Visit Twitter Office to Review Code for Musk by netmonk on Friday October 28, 2022 @06:32AM (#33369674)

similar workload is live update trafic monitoring. collect data from all agents, and redistribute aggregated/processed data to all agent, and update route to optimise time or length or both of travel. collecting data, ingesting data, redistributing ingested/processed data.

I remember back on 2015, there was an AMA on reddit from a former engineer from Telsa.

I remember clearly how he explained how Telsa struggled to update thousand of car's firmware with legacy RH5 vm running on amazon and openssl 0.98 incompatibility with upper version.

I found it very amusing, cause at the same time, i was working at one of the leader of payment industry and POS maker. And we where exactly struggling with the same issue updating firmware of hundred thousand POS terminal in the wild (except that our servers where on premise and not at aws)and dealing with this openssl issue.

[ Parent | on HN ]