Timeline for Algorithm for Dynamic Client Side Throttling
Current License: CC BY-SA 3.0
24 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:37 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| S Jun 10, 2015 at 15:10 | history | bounty ended | Animal Style | ||
| S Jun 10, 2015 at 15:10 | history | notice removed | Animal Style | ||
| Jun 5, 2015 at 16:52 | answer | added | vzn | timeline score: 4 | |
| Jun 5, 2015 at 16:43 | comment | added | vzn | would like to try out some ideas interactively if you visit Computer Science Chat. meantime will post a preliminary idea that seems workable. it could be better tuned with more feedback/ analysis. | |
| Jun 5, 2015 at 0:19 | history | edited | Animal Style | CC BY-SA 3.0 |
added 2 characters in body
|
| Jun 5, 2015 at 0:14 | answer | added | Kyle Jones | timeline score: 2 | |
| Jun 4, 2015 at 23:22 | history | edited | Animal Style | CC BY-SA 3.0 |
added 1133 characters in body
|
| Jun 3, 2015 at 23:53 | history | edited | Animal Style | CC BY-SA 3.0 |
deleted 56 characters in body
|
| Jun 3, 2015 at 23:40 | history | tweeted | twitter.com/#!/StackCompSci/status/606244078464958465 | ||
| Jun 3, 2015 at 23:13 | comment | added | Animal Style | @vzn I added a section above that gives more details on my scenario, let me know if you need more information. | |
| Jun 3, 2015 at 23:11 | history | edited | Animal Style | CC BY-SA 3.0 |
added 600 characters in body
|
| Jun 3, 2015 at 23:00 | comment | added | vzn | do the responses have the same size? a key question is what contents of the request have effects on response times and or size of response. eg form submissions, XML requests etc... this project could benefit from some extended empirical analysis via graphs etc... possibly more to analyze in Computer Science Chat | |
| Jun 3, 2015 at 22:44 | comment | added | Animal Style | @vzn Should have said Response times are unpredictable, meaning that depending on the request the server has to do a variable amount of work which takes between 7 and 90 seconds to get a response back to the client. The client can send out requests really fast. | |
| Jun 3, 2015 at 22:28 | history | edited | Animal Style | CC BY-SA 3.0 |
edited body
|
| Jun 3, 2015 at 22:13 | comment | added | vzn | "Requests times are unpredictable and can be between 7 and 90 seconds." do you mean the time between requests? this is a fairly straightfwd application of some basic control theory concepts... may write this up further later | |
| S Jun 3, 2015 at 17:54 | history | bounty started | Animal Style | ||
| S Jun 3, 2015 at 17:54 | history | notice added | Animal Style | Draw attention | |
| Jun 2, 2015 at 13:37 | comment | added | Animal Style | @jkff If by model you mean keeping track of the time spent on each request, that is what I am adding to the rolling average and using as a comparison. I think what is happening is the server tries to process all requests at once and gets bogged down context switching. At a high number of outstanding requests the response times actually increase drastically. So keeping the server overly full has a negative impact in this case. | |
| Jun 2, 2015 at 10:24 | history | edited | Raphael |
edited tags
|
|
| Jun 2, 2015 at 4:39 | comment | added | jkff | You need to have a model for the time it takes the server to process each request. Clearly it is dependent on the number of requests the server is currently processing, but in what way? E.g. can we simply assume that the server has a certain internal parallelism and everything else is queued? In that case the throughput would be the same as long as you keep the server fully loaded, only latency would suffer. | |
| Jun 1, 2015 at 18:11 | history | edited | Animal Style | CC BY-SA 3.0 |
edited body
|
| Jun 1, 2015 at 17:54 | review | First posts | |||
| Jun 1, 2015 at 18:05 | |||||
| Jun 1, 2015 at 17:53 | history | asked | Animal Style | CC BY-SA 3.0 |