| | 1 | = Extending log information in the BOINC client = |
| | 2 | == Motivation == |
| | 3 | Current available traces contain the availability information about the participants. More information would be useful to improve the allocation of jobs and the checkpoint mechanism. For example, the time wasted by the interruptions could be analyzed in order to determine the best checkpoint period. |
| | 4 | |
| | 5 | == Additional information == |
| | 6 | The following information could be saved on each client: |
| | 7 | * job scheduling actions (start/stop/exit of jobs with the ID of the related jobs) |
| | 8 | * checkpointing events |
| | 9 | * change in fraction done of running jobs |
| | 10 | |
| | 11 | == Retrieving the data == |
| | 12 | Retrieving these data represents a traffic that the server may not be able to support. Several non-exclusive solutions are possible: |
| | 13 | * retrieve only a subset of the log (e.g., only job scheduling actions) |
| | 14 | * retrieve only data that are new |
| | 15 | * compact the log |
| | 16 | * sample the clients for which the log is retrieved |
| | 17 | * based on a period, but the retrieved log will not be representative of participants that have a low rate of connection to the server |
| | 18 | * based on the user ID |
| | 19 | * request the log only when it reaches a significant size to avoid multiple small transfers |
