4 ms·
It is way more than 1.4TBs a second globally.
by cortesoft 4y ago
It is way more than 1.4TBs a second globally.
- xyzzy123 4y agoI wonder how much is api traffic and how much is assets & images.
- koolba 4y agoI wonder how much of that is crypto spam bots replying to each other.
- skywhopper 4y agoCan you detect and block those spam bots with less effort than it would take to process them?
- koolba 4y agoThat’s a not so simple calculation as comparing the raw request process time isn’t the complete picture. Spam bot content must be persistently stored, indexed, archived, etc so the long term cost is much more than the one off POST to create the entity. You’d also have to quantify the improved user experience from seeing less spam v.s. inflated ad revenue for garbage views / content.
- deleted 4y ago[deleted]
- _zoltan_ 4y agoin this specific discussion it's very important to use Tb and TB correctly.
- Gigachad 4y agoThis is never going to happen. If I want to indicate it's correct I'd write Tbit/s or Tbyte/s. Otherwise its a coin flip if TB and Tb has been used correctly.
- jrockway 4y agoI like /s for bytes and ps for bits. 100Mbps = 100 million bits per second. 100MB/s = 100 million bytes per second. (The capitalization is important of course. I tried writing some examples where it's not preserved and it's too weird. I tend to not use capital letters on things like Slack, but for bytes, you just have to. The difference between milli and Mega can also be important, but since nobody talks about the negative powers with bandwidth, you are probably OK if your shift key breaks.)