I've heard that list sizes greater than 150K-200K start to return timeouts at higher rates. Although I'd enjoy hearing first-hand experiences and recommendations. Thanks, Doug
On Wed, Jun 3, 2009 at 9:19 PM, Jesse Stay <jesses...@gmail.com> wrote: > In my case specifically it's the Social Graph methods. I didn't realize > you had paging available now. Is there some logic as to when I should > expect to page and when I can just rely on the full result? > Jesse > > > On Wed, Jun 3, 2009 at 9:56 PM, Doug Williams <d...@twitter.com> wrote: > >> What methods in particular are you referring to? The social graph methods >> now support paging so retrieving all of that data is now possible, where it >> used to throw 502s. It does however require a bit of application logic to >> assume when paging is necessary (e.g. large follower counts). Additionally, >> we are making changes to the databases which cause latency that result in >> periodic 502s. We are not able to give definitive ETAs on these fixes due to >> priorities that change as unforeseeable critical needs arise. >> More specificity would be beneficial. Do you have a replaceable bug, >> problem, or suggestion that you would like to discuss? >> Thanks, >> Doug >> >> >> >> On Wed, Jun 3, 2009 at 7:22 PM, Jesse Stay <jesses...@gmail.com> wrote: >> >>> I was discussing this with Iain, and have also talked about it with >>> Damon, so I know I'm not alone in this. I am having huge issues retrieving >>> follower and friend data for the larger users (1 million+ followers), most >>> of the time returning 502 Bad Gateway errors. I know there are a few of >>> these users getting really frustrated about our apps not being able to >>> retrieve data for them. Is there a plan to fix this? Is the API team aware >>> of this? Any ETA by chance? >>> Thanks, >>> >>> @Jesse >>> >> >> >
