The current (6.13) BOINC client doesn't support sticky generated files, as you describe them. It also doesn't support files that are both uploaded and downloaded (as required for "distributed storage" purposes).
Here's a design doc for client changes that will fix both problems: http://boinc.berkeley.edu/trac/wiki/ClientDataModel Comments welcome. -- DPA Note: it took me almost 4 years to deal with this. Better late than never! On 12-Oct-2007 7:45 PM, Nicolas Alvarez wrote: > I was wondering if the core client handled in the "expected way" a few > uncommon combinations of file flags. For example, what happens if > there is an output file without<upload_when_present/>? One > combination I'm interested in is for a file that can be generated, but > it's too big to have the client download it. On the other hand, it > also takes a while to generate, so I wouldn't want to re-generate it > on each workunit. > > I'd use an output file with these flags: > <generated_locally/> > <sticky/> > > I don't want it to upload when workunit finishes, just to stay in the > project directory, so there is no upload_when_present. The next > workunit would use it as input. I can't use an input file, since it > would be required to exist on the first workunit too, and all input > files are downloaded (actually... what happens if an input file has > <generated_locally>?). > > Another example adding<report_on_rpc/>, for locality scheduling where > the big input file is generated, not downloaded: > > There are ten batches of 100 workunits. Each batch has a different > file that it can generate and reuse later. Client downloads > batch3_w42. The app notices the cache_3 file doesn't exist, so it > generates it, and then processes it. Next time the client asks for > work, it would report the existence of cache_3 (because of > report_on_rpc), and the scheduler would try to send another workunit > from the same batch. Client gets batch3_w19, loads the cache_3 file, > and processes it. Client asks for work again. There isn't any more > work for that batch, so scheduler sends batch4_w76 and request > deletion of cache_3. > > Is this currently possible? I'm asking about the client side. > Specifically: correct behavior on an output file that doesn't get > uploaded and is sticky, and/or an input file that is > generated_locally. If it's not, consider this a feature request. > _______________________________________________ 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.
