Max: Currently the server's calculation of disk requirements is crude, and doesn't handle your case well.
I'll modify the scheduler so that takes into account sticky files (including their possible presence on the client). However, this may take me a month or two. -- David On 19-Oct-2011 5:06 AM, Max Dmitrichenko wrote: > Hi! > > In my project I use sticky files - they are quite big (hundreds of MB) > but are shared among many workunits. > When I create a workunit I specify the rsc_disk_bound equal to the sum > of all input files size plus expected > size of all outputs. So every workunit has rsc_disk_bound set to approx. 1GB. > > This has bad effect on scheduler, since it decides to send 3 WU to the > client if it has 3 GB of free disc space. > But among this 3 GB about 2.7 GB are shared sticky files which usually > already are on the client. Should > I not include shared sticky files sizes to rsc_disk_bound? What > happens then if client doesn't have this sticky > files downloaded and there is no space for the whole WU including the > sticky files? > > -- > Max > _______________________________________________ > 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. _______________________________________________ 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.
