Hey Ed,

We're still aiming for raising OAuth limits but don't have a time table yet.
Given our experiences with rate limits, World Cup, and our desire for system
stability, I can imagine us staggering the roll out similar to your
suggestions. We'll reinvestigate raising limits after the company-wide
efforts to stabilize the platform are realized.

Taylor

On Mon, Aug 30, 2010 at 10:40 AM, M. Edward (Ed) Borasky <
zn...@borasky-research.net> wrote:

> Now that oAuthpocalypse is approaching a successful finish, what's the plan
> for "Inverse oAuthpocalypse?" That is, we were promised that the API call
> rate would rise to 1500 GETs per hour on oAuth. It is currently at 350, and
> dropped to 175 at one point during the World Cup Loadapalooza. So is there a
> plan to gradually get up to the 1500, will we see a jump to 1500, or are we
> stuck at 350 for the foreseeable future?
>
> As a developer and former capacity planner, my preference would be for a
> very gradual increase - say increases of 50 an hour per week until something
> breaks, then hold there as dictated by infrastructure growth priorities.
>
> --
> M. Edward (Ed) Borasky
> http://borasky-research.net http://twitter.com/znmeb
>
> "A mathematician is a device for turning coffee into theorems." - Paul
> Erdos
>
>
>
>
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk?hl=en
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Reply via email to