Max. runtime of v3.42?

Message boards : Number crunching : Max. runtime of v3.42?
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Dirk Sadowski
 

Send message
Joined: 28 Mar 10
Posts: 21
Credit: 223,324
RAC: 48
Message 1025 - Posted: 9 Mar 2013, 15:10:08 UTC

Currently I don't have continuously internet connection.

What's the max. runtime of the v3.42 Windows app?

My BOINC got after:
10h:08m:04s elapsed - 12s CPU - time
...and...
9h:41m:17s elapsed - 5s CPU - time
...computation errors:

<core_client_version>7.0.52</core_client_version>
<![CDATA[
<message>
Maximum disk usage exceeded
</message>
<stderr_txt>
(...)


Which runtime would be fine, for not to get an error?
6, 7 or 8 hours?

Maybe it's possible to edit the client_state.xml for to increase the max. disk usage value, so I could let run the app at least 24 hours?
Because normally I go currently 1 time/day online.

Thanks.

BTW.
Maybe for people which can go only 1 time/day online, it would be possible to get them 8 WUs in a bunch?

ID: 1025 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile STE\/E
             
Avatar

Send message
Joined: 28 Mar 10
Posts: 671
Credit: 3,989,329
RAC: 686
Message 1026 - Posted: 9 Mar 2013, 15:38:39 UTC

ID: 1026 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
BobCat13
 

Send message
Joined: 6 Apr 10
Posts: 27
Credit: 529,824
RAC: 46
Message 1027 - Posted: 9 Mar 2013, 15:44:35 UTC - in response to Message 1025.  
Last modified: 9 Mar 2013, 15:48:06 UTC

If you are willing to edit the client_state.xml file,

1. stop the client
2. open client_state.xml in a text editor, i.e. Notepad
3. find WUProp project section and then locate <workunit> part
4. change the <rsc_disk_bound> by adding a 0 (zero) after the 1 to change it from one million bytes to ten million bytes.
5. save the client_state.xml, making sure the file extension does not change
6. start the client

I'm not sure there is a time limit to how long tasks can run, as I was without internet access for over a day, so my WUProp task reached over 27 hours and didn't error and validated when returned.

Edit: Looking at client_state.xml, there is a maximum runtime limit <rsc_fpops_bound>, but that number is so high that the deadline will likely pass before reaching that number of flops.
ID: 1027 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Link
 
Avatar

Send message
Joined: 20 Jun 12
Posts: 142
Credit: 342,074
RAC: 65
Message 1030 - Posted: 9 Mar 2013, 20:41:53 UTC - in response to Message 1027.  

1. stop the client
2. open client_state.xml in a text editor, i.e. Notepad
3. find WUProp project section and then locate <workunit> part
4. change the <rsc_disk_bound> by adding a 0 (zero) after the 1 to change it from one million bytes to ten million bytes.
5. save the client_state.xml, making sure the file extension does not change
6. start the client

Either that, or you watch the size of the output file in the wuprop directory, sould be something like wu_v3_1362550290_148687_0_0. This file grows on every computer at different speed, depending of what and how many projects are running and how many WUs are running together. In case of your machine the limit seems to be somewhere around 9 hours. Remember when increasing the max. file size in client_state.xml, that you have to upload that file. Uploading several MBs with a 56k modem isn't that funny.
ID: 1030 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Max. runtime of v3.42?

©2024 Sébastien