| 3 | | BOINC was originally designed for high-throughput computing, and one of its basic design goals was to minimize the number of scheduler RPCs (in order to reduce server load and increase scalability). In particular, when a client requests work from a server and there is none, the client uses exponential backoff, up to a maximum backoff off 1 day or so. This policy limits the number of scheduler requests to (roughly) one per job. However, this backoff policy is inappropriate for '''low-latency''' computing, by which we main projects whose tasks must be completed in a few minutes or hours. Such projects require a '''minimum connection rate''', rather than seeking to minimize the connection rate. |
| | 3 | BOINC was originally designed for high-throughput computing, and one of its basic design goals was to minimize the number of scheduler RPCs (in order to reduce server load and increase scalability). In particular, when a client requests work from a server and there is none, the client uses exponential backoff, up to a maximum backoff off 1 day or so. This policy limits the number of scheduler requests to (roughly) one per job. However, this backoff policy is inappropriate for '''low-latency''' computing, by which we mean projects whose tasks must be completed in a few minutes or hours. Such projects require a '''minimum connection rate''', rather than seeking to minimize the connection rate. |
