1) Message boards : Questions and problems : How do 'daily schedule' network limits and high priority WUs interact? And do projects care if you heavily throttle transfers? (Message 71073) Posted 29 Jul 2016 by MikeHG Post: Les: Ha! Yes, I'm in the UK, and I think climateprediction is in Oxford, so I guess that's why I can get relatively good throughput there. Slow is relative, no doubt, and that plus rtorrent is enough to interfere with Netflix with two people in the flat. Didn't mean to seem ungrateful ;) Mark: It's a headless virtual server, so 'interactive' stuff is out unfortunately. I guess what I'll have to do is limit it to 100 K/sec or something, then tell it to run from midnight ish to dinner time ish. Can't imagine I'll miss too many deadlines like that. I still think it'd be good to either have separate up / down schedules, or have the option to override schedules automatically for late tasks, but I'm sure this'll work. Thanks both for the replies.

2) Message boards : Questions and problems : How do 'daily schedule' network limits and high priority WUs interact? And do projects care if you heavily throttle transfers? (Message 71060) Posted 28 Jul 2016 by MikeHG Post: Hi, Short version: if I've got a WU which has gone into high priority, then finishes during a period when I've told BOINC not to transfer files, what happens? And does it cause extra stress to project servers throttling transfers to something very low like 50 - 100 K/sec? Long version: My network isn't that fast, and sometimes I want to watch streamed films or something. I don't want to unnecessarily strain BOINC project servers by throttling to something ridiculously low (presumably they have a limited number of concurrent connections, so up / downloading a big WU from climateprediction.net at 50 K/sec seems like taking the Mickey, though maybe I'm wrong and they really don't care?) An obvious answer would be to limit file transfers to hours when I'm sleeping. But I'm wondering whether that'll mean that WUs miss their deadlines, and are unnecessarily replicated. Some previous threads seem to indicate that notifying the project that the WU has completed and uploading it are separate tasks. Does limiting file transfer times affect the former? I wonder whether there is extra justification for separating upload / download limits for this reason, and there's some previous discussion here: https://boinc.berkeley.edu/dev/forum_thread.php?id=10994 . Another alternative might be to have a checkbox on the network schedule page saying something like 'ignore for overdue tasks', though I realise that ideas are great and all but they don't magically implement themselves. Thanks for any insight anyone can provide - and thanks generally to BOINC! boinc --version 7.6.33 x86_64-pc-linux-gnu

---

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.