Timeline for Why does the /events service sometimes pause for a couple of minutes?
Current License: CC BY-SA 3.0
9 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/
|
|
| Jan 3, 2015 at 18:15 | history | edited | Brock Adams |
edited tags
|
|
| May 22, 2012 at 19:59 | vote | accept | Greg Hewgill | ||
| May 22, 2012 at 19:53 | answer | added | Kevin Montrose | timeline score: 3 | |
| May 22, 2012 at 19:51 | history | edited | Kevin Montrose |
edited tags
|
|
| Apr 20, 2012 at 20:45 | comment | added | Greg Hewgill |
@russau: I think you're on to something. I tried adding a random nonce= parameter to the query, but that didn't seem to help. Then I tried decreasing the since= parameter by 1 every time I got no results, and that does seem to avoid this problem (and I now get individual periods with no new events).
|
|
| Apr 20, 2012 at 19:51 | comment | added | Greg Hewgill |
@russau: That's a good point. If the caching is done at a layer above the API request handler, and during some 10-second period there is no new activity, then subsequent requests will use the same since field. That would explain why I never see single 10-second periods with 0 new events.
|
|
| Apr 20, 2012 at 14:02 | comment | added | russau |
i just read this in the docs "the Stack Exchange employs heavy caching and as such no application should make semantically identical requests more than once a minute. This is generally a waste of bandwidth, as more often than not the exact same result will be returned." the since filter is being applied to the cache contents and you are 'overtaking' the cache?
|
|
| Apr 18, 2012 at 0:34 | history | asked | Greg Hewgill | CC BY-SA 3.0 |