3 ms·
1500 bytes is a pretty big average payload size when you consider information theory and what actually must be communicated for this kind of business (on averag
by bob1029 5y ago
1500 bytes is a pretty big average payload size when you consider information theory and what actually must be communicated for this kind of business (on average).
A user clicking "Watch later" on a video could theoretically be communicated in something as small as 64-bit integer for the user/session id, one for the command type, and another for the identity of the actual video. With serialization, padding, etc., you are still probably well under 50 bytes for this one event.
Being sloppy with data throughout is certainly a good reason to need more pipes and servers. With enough discipline, you can process events at rates far exceeding 1 million per second with a single box and non-exotic network stack.
- TheCoelacanth 5y ago1500 bytes isn't even enough to send a list of video titles and thumbnail images for a single page of videos. If you imagine that the client already has a full database of all the available videos and metadata about them, then you could get by with tiny amounts of data, but that's not even close to the actual circumstances that Netflix operates under.