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 optimiza
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 ne
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
iss
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
