Re:Twitter says they fixed the Memcache calcification proble...
by achompas on Wednesday July 11, 2012 @03:24AM
(#4228205)
Are you talking about 15B vs. the visits chart I linked? If so, the 15B number comes from API calls, which do not have to happen through the website (think of all the Twitter clients).
In an RTB environment, there is an additional constraint of having to serve up your ad (or decision) within 60ms (Google ADX sets a hard limit of 80ms), and the fastest best bid wins.
I don't think that's a less hard problem compared to Twitter, especially at high volumes. You can't just say "scale sideward!".
That said, the first link was totally misleading. I was actually quite shocked to see that Twitter only had 42M uniques per month, because a typical ad network does a lot more
EDIT: ah.. 15B requests/day makes more sense. Wtf is with the wrong stats?