There is also the problem of the scheduler on the client. It is not set up for an arbitrary amount of work.
What do you tell it for the amount of work to be done, and what do you tell it for the deadline. This will affect how your task and tasks from other projects get scheduled. From: Jon Sonntag [mailto:[email protected]] Sent: Monday, April 15, 2013 10:39 AM To: McLeod, John Cc: Henri Heinonen; BOINC Developers Mailing List Subject: Re: [boinc_dev] WrapperApp questions BitTornado is a Bit Torrent client for peer to peer file sharing. I have yet to see a bit torrent client that is a GPU application. For the issue with many files and directories, you would probably want to use the zip file/folder features. That way, your app only needs to include the name of the zip file but you can put whatever you want into it. While what John says is true about communications being initiated by the client, there is a way, at least kind of.... The app would have to be set up to do trickle updates so the client will get credit every so often. I'm not sure whether trickle credit can be done via the wrapper though. You would need to have some type of daemon run on the server which can cancel the WUs. when you want them to stop. You should also consider awarding credit from the time of the last trickle update to the time the WU was cancelled by the server. So, the server can't make it stop immediately. It would have to wait for the client to do a scheduled update. It isn't a perfect solution, but that might get you started. Jon Sonntag On Mon, Apr 15, 2013 at 8:56 AM, McLeod, John <[email protected]<mailto:[email protected]>> wrote: The BOINC server cannot send a signal to the client. All communications must be initiated by the client. Please don't have GPU applications that run forever, that will tend to limit the availability of the GPU to other projects. -----Original Message----- From: boinc_dev [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Henri Heinonen Sent: Sunday, April 14, 2013 5:36 AM To: BOINC Developers Mailing List Subject: [boinc_dev] WrapperApp questions Hi! How can I run a BOINC GPU application that never ends? How can I eventually send the signal from my BOINC server to end the workunit? I'm planning to use WrapperApp ( http://boinc.berkeley.edu/trac/wiki/WrapperApp ) to start this Windows program: "BitTornado.exe -h yourhost -u username -p password" If my worker program (BitTornado.exe) has many files and subdirectories, how can I include them? Is this the correct way to do the *worker_job_1.0.xml?* <job_desc> <task> <application>worker</application> <command_line>-h yourhost -u username -p password</command_line> </task> </job_desc> _______________________________________________ boinc_dev mailing list [email protected]<mailto:[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]<mailto:[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.
