Re: [twitter-dev] lockouts are the new black
These lockouts are almost certainly due to a performance optimization intended to reduce network utilization by increasing physical reference locality in a multi-level loosely-coordinated best-effort distributed cache. Not easy to get right, and the engineers involved are working to resolve the issue. There's absolutely no intention to lock people out. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, Jul 6, 2010 at 9:00 AM, Isaiah Carew wrote: > > Lockouts are now common and frequent for everyday users doing normal > things. > > I have dozens of reports from my users being locked out. And I've noticed > that nearly every Twitter client developer has posted about this in a blog > or Tweet. Several in just the last 24 hours. > > I know that the goal is to improve the latency and failures (i.e. "whales") > that you guys were seeing during the world cup. But creating lockouts to > reduce failures is cutting off your nose to spite your face. > > Failures, lagging, and latency are frustrating but at least *feel* > egalitarian. Service disruption is nothing new -- we understand it whether > it's AT&T, temporary power failures, or whatever. > > *Lockouts feel punitive and targeted. Users really really don't like it.* > > I think it's safe to say that this is now *the* critical issue. All other > twitter concerns seem dwarfed by this massive problem. > > isaiah > http://twitter.com/isaiah > >
Re: [twitter-dev] lockouts are the new black
With "multi-level loosely-coordinated best-effort distributed cache" you certainly got the naming, all that's left is the cache invalidation. :) Pascal On Jul 6, 2010, at 18:10 , John Kalucki wrote: > These lockouts are almost certainly due to a performance optimization > intended to reduce network utilization by increasing physical reference > locality in a multi-level loosely-coordinated best-effort distributed cache. > Not easy to get right, and the engineers involved are working to resolve the > issue. There's absolutely no intention to lock people out. > > -John Kalucki > http://twitter.com/jkalucki > Infrastructure, Twitter Inc. >
Re: [twitter-dev] lockouts are the new black
John, Do you measure the number of lockouts? Or maybe a better question is: do you have metrics on how reducing rate limits is impacting users? isaiah http://twitter.com/isaiah On Jul 6, 2010, at 9:10 AM, John Kalucki wrote: > These lockouts are almost certainly due to a performance optimization > intended to reduce network utilization by increasing physical reference > locality in a multi-level loosely-coordinated best-effort distributed cache. > Not easy to get right, and the engineers involved are working to resolve the > issue. There's absolutely no intention to lock people out. > > -John Kalucki > http://twitter.com/jkalucki > Infrastructure, Twitter Inc. > > > > On Tue, Jul 6, 2010 at 9:00 AM, Isaiah Carew wrote: > > Lockouts are now common and frequent for everyday users doing normal things. > > I have dozens of reports from my users being locked out. And I've noticed > that nearly every Twitter client developer has posted about this in a blog or > Tweet. Several in just the last 24 hours. > > I know that the goal is to improve the latency and failures (i.e. "whales") > that you guys were seeing during the world cup. But creating lockouts to > reduce failures is cutting off your nose to spite your face. > > Failures, lagging, and latency are frustrating but at least *feel* > egalitarian. Service disruption is nothing new -- we understand it whether > it's AT&T, temporary power failures, or whatever. > > Lockouts feel punitive and targeted. Users really really don't like it. > > I think it's safe to say that this is now *the* critical issue. All other > twitter concerns seem dwarfed by this massive problem. > > isaiah > http://twitter.com/isaiah > >
