> sometimes amounting to over 100 gigabytes each second. So that's 800 gigabits per second, nearly a Tbps. Which is a lot of network throughput. Although thi

> sometimes amounting to over 100 gigabytes each second. So that's 800 gigabits per second, nearly a Tbps. Which is a lot of network throughput. Although this is not impossible, it seems surprisingly high, and I wonder if the article should have said "100 gigabits each second", which is still a lot of bandwidth but a little more reasonable. The article describes the data being transmitted as largely telemetry. Let's say they are sampling each of their metrics every 10 milliseconds (100/second), and they need a 32 bit integer to store each value. So, that's 100 * 32 / 8 = 400 bytes per second per metric. Divided into 100 gigabytes, that would be 250 million metrics. Even if you change these assumptions, clearly this link is used for more than telemetry. 800 Gbps requires a large number of computers to generate and transmit, then another large set of machines at HQ to ingest all that data and then run analytical models against it. Just to handle the network traffic, without any data analysis, if you assume servers have a pair of 10 Gbps network interfaces, that's 40 machines. If you assume hard drives can write at about 100 megabytes per second, that's 1,000 disks just to handle the write IOPS. But, with those 40 machines, that's an average of 25 disks per machine, so not unreasonable. With SSD's it would be fewer devices. I do not know if a way to get this much network throughput over a radio link, so I can't imagine it's all coming from the car itself. It would be interested to know what other data is transmitted over this link during a race other than telemetry.