Timeline for Algorithm for Dynamic Client Side Throttling
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Aug 11, 2016 at 13:04 | history | suggested | SaveTheRbtz | CC BY-SA 3.0 |
fixed mistype
|
| Aug 11, 2016 at 10:32 | review | Suggested edits | |||
| S Aug 11, 2016 at 13:04 | |||||
| Jun 10, 2015 at 15:10 | history | bounty ended | Animal Style | ||
| Jun 8, 2015 at 19:31 | comment | added | Animal Style | This sounds like the way to go and is similar to what I was trying with a moving average. The problem I have so far with this approach is picking a size for the running average, X last response times, and incorporating the lowest response times into the average. When I have run variations the average is slow to go up and thus allows many requests out at once which, in the long run, creates a high average and ultimately explodes. I will continue to experiment with this approach. | |
| Jun 5, 2015 at 16:52 | history | answered | vzn | CC BY-SA 3.0 |