I checked in a change so that limits on the number of active
per-project and total file transfers
don't include user files (like background images for SETI@home graphics)
or project files (like images for the simple GUI)
-- David
On 12/24/2015 4:41 AM, Jord van der Elst wrote:
Hi guys,
Something that's slowly been developing and is starting to be a problem with more
and more projects. When for whatever reason the small image files for Simple View
do not download correctly, they get shown as 'some download is stalled' in BOINC
Manager and all subsequent downloads of work is stalled as well. This causes
systems to run out of work.
I think we should rethink this, and not have image files of a part of the GUI that
not everyone uses/sees, be capable of having a catastrophic effect on work downloads.
Two threads about this, one in the BOINC forums:
https://boinc.berkeley.edu/dev/forum_thread.php?id=10691
And one in the WCG forum:
https://secure.worldcommunitygrid.org/forums/wcg/viewthread_thread,38704
In the latter, Sekerob shows how to circumvent this problem by downloading the
image files by hand, but people shouldn't have to go through this. Not with BOINC
needing to be set & go.
Two solutions come to mind:
1. Don't let image files be dependent on downloads. If one or more are stuck, too
bad but they're not crucial for the client to run, so dismiss that they're not in
yet and always allow downloads of applications/work to continue.
2. Compress the image files into a zip file, download that separately from work
requests, unpack at BOINCs leisure.
Or perhaps:
3. Have a check in place to see what view the user uses. If not Simple View, is it
necessary to download all image files now, or can we spread them over further
downloads of work, and still separate their outcome from work requests?
Discuss!
(Heh, always wanted to say that. :-))
With seasonal greetings,
-- Jord van der Elst.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
