2 ms·
> 200 million/sec OK, but you aren’t just pushing raw ASCII across the wire, you’re getting those results out of a database. For a weekend clone, someone will
by sgarland 3y ago
> 200 million/sec
OK, but you aren’t just pushing raw ASCII across the wire, you’re getting those results out of a database.
For a weekend clone, someone will probably just use an RDBMS (a very reasonable choice). I’ll be generous and say they can retrieve a given tweet in sub-msec time, say 10 usec. Suddenly, you can only send 100,000 tweets/sec, ignoring all other overhead (which of course you can’t).
I’m sure there is unoptimized code and some unnecessary bloat, but fundamentally there are limits on data retrieval that are very, very hard to get close to.