Timeline for new throttle does not differentiate between api requests and requests made from viewing the site
Current License: CC BY-SA 2.5
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:25 | history | edited | CommunityBot |
replaced http://stackapps.com/ with https://stackapps.com/
|
|
| Sep 5, 2010 at 16:17 | history | edited | Sky Sanders | CC BY-SA 2.5 |
added 939 characters in body
|
| Aug 29, 2010 at 21:29 | comment | added | Nathan Osman | @code: Hope my answer below helps... hope I'm not doing something wrong. | |
| Aug 29, 2010 at 21:28 | answer | added | Nathan Osman | timeline score: 1 | |
| Aug 29, 2010 at 16:25 | comment | added | Nathan Osman | @code: Okay, I'll rerun them in a bit. One small sidenote: I was unable to reproduce the browser issue - what steps are needed for that? | |
| Aug 29, 2010 at 9:49 | comment | added | Sky Sanders | @geo - and really, an app does not have to be a quota hog. 2 apps making 20 requests within 5 seconds of each other will kill them both and the browser. This makes a case for the most obvious solution of the api server introducing latency instead of forcing the developer to implement throttling, but that is another issue. The one at hand is determining if the current API throttle is operating to spec. | |
| Aug 29, 2010 at 9:45 | comment | added | Sky Sanders | @geo - and it should be obvious that you should not have any other apps that use the API running when you test. That brings up another sticky issue for developers; what if a user is running more than one distinct app? hmmm.... looks like we have to add a warning line to an apps readme if our app is a quota hog. And could you please post your results as an answer on the other post? | |
| Aug 29, 2010 at 9:41 | comment | added | Sky Sanders | @geo - that you are failing on the same request each time is weird and that you are getting a failure at all with 6.5 is even more weird, as this seems to be the current viable threshold. it sounds like you might not have waited 30 seconds between tests. if you go too early, before the throttle has cooled down, you get a delay but and an alert but no test is actually run - notice the first 2 lines in the log, they will tell you what rate is set for the Soapi throttle. If you could try it again and wait 30 seconds between tests you should get valid results. thanks for running the tests. | |
| Aug 29, 2010 at 6:40 | comment | added | Nathan Osman |
@code: Okay, for '30 req. / 5 sec.', I got an error for request #31. For '30 req. / 5.5 sec.', I got an error for request #32. For '30 req. / 6 sec.', I got an error for request #31. And for '30 req. / 6.5 sec.', I got an error for request #31 again. Hope that helps... and I hope I did it right :)
|
|
| Aug 29, 2010 at 1:42 | comment | added | Sky Sanders | @geo and kevin - confirm no-repro. George, your results from stackapps.com/questions/1457 would be appreciated. | |
| Aug 29, 2010 at 1:41 | history | edited | Sky Sanders | CC BY-SA 2.5 |
added 733 characters in body
|
| Aug 29, 2010 at 1:29 | comment | added | Sky Sanders | @kevin and george, I am now having a hard time producing a repro case of browsing affecting api quota myself. Let me get back to you. this may be a non-issue. | |
| Aug 29, 2010 at 1:19 | comment | added | Nathan Osman | @code: If you can point me to a JS page that pushes beyond the throttle, I'll give it a try and see if I can reproduce it. | |
| Aug 29, 2010 at 1:15 | comment | added | Sky Sanders | @kevin - but it works the other way around, browsing while using an app, over which app developers have no control leading to an uncontrollable risk of denial to both the app and the browser. There is a clear delineation between api usage and web browsing. | |
| Aug 29, 2010 at 1:09 | comment | added | Kevin Montrose | @code poet - what you're describing is not a violation of the published throttle guidelines. If you "trip the wire" we reserve the right to do anything, which includes a network wide ban given that its a thing. | |
| Aug 29, 2010 at 1:00 | comment | added | Sky Sanders | @kevin - trip the wire with api requests and then try to browse a site. i think you will find a repro going that direction. the other direction is a less common story but the difference is academic. | |
| Aug 29, 2010 at 0:30 | history | edited | Kevin Montrose |
edited tags
|
|
| Aug 28, 2010 at 19:58 | history | edited | Sky Sanders | CC BY-SA 2.5 |
added 118 characters in body
|
| Aug 28, 2010 at 19:46 | history | asked | Sky Sanders | CC BY-SA 2.5 |