Thread 'BOINC network/cpu times'

Message boards : BOINC Manager : BOINC network/cpu times
Message board moderation

To post messages, you must log in.

AuthorMessage
MarkJ
Volunteer tester
Help desk expert

Send message
Joined: 5 Mar 08
Posts: 272
Australia
Message 16520 - Posted: 8 Apr 2008, 7:09:03 UTC

I posted this over at S@H but as pointed out to me this is the best place to mention BOINC problems.

When I set the "network usage allowed" times they don't seem to work with certain combinations.

In boingmgr -> advanced -> preferences and click on the network usage tab (also does this for processor usage). Select time examples as below, click the okay button. Reselect and they have changed.

06:20/22:20 becomes 06:19/22:19.
06:35/22:35 becomes 06:34/22:34.
06:50/22:50 becomes 06:49/22:49.

The times are stored in decimal, when they are converted back to a time they are not shown correctly.

06:20 is stored as 6.333333 and when it converts from decimal back to a time it stuffs them up (ie .333333 x 60 mins = 19.999998) so it shows as 06:19.

See global_pref_override.xml exerpt below. I have seen this using BOINC versions 5.10.30 and 5.10.45 under Windows.

<global_preferences>
<run_on_batteries>0</run_on_batteries>
<run_if_user_active>0</run_if_user_active>
<idle_time_to_run>3.000000</idle_time_to_run>
<start_hour>0.000000</start_hour>
<end_hour>0.000000</end_hour>
<net_start_hour>6.333333</net_start_hour>
<net_end_hour>22.333333</net_end_hour>


Hoping someone will pick this up and raise a trac.

Thanks
ID: 16520 · Report as offensive
MarkJ
Volunteer tester
Help desk expert

Send message
Joined: 5 Mar 08
Posts: 272
Australia
Message 16522 - Posted: 8 Apr 2008, 9:04:21 UTC - in response to Message 16521.  

To confirm seen this on windows with several 5.10.xx releases and just tested on 6.1.12 it does same. It's only effecting the number displayed. The stored value is still correct, until any other value is changed, at which time it saves the 6:19 equivalent.... 6.316668


Yes it could compound the problem if you just clicked okay after it had read back the prefs as 06:19, ad infinitum...

I have crunch3r's BOINC 6.1.0 on one machine and it does exactly the same.

Also I can confirm that it does use 06:19 as the time to resume network traffic as seen from the log entries:

8/04/2008 4:56:10 AM|Einstein@Home|Starting task h1_0923.55_S5R3__374_S5R3b_0 using einstein_S5R3 version 436
8/04/2008 6:19:01 AM||Resuming network activity
8/04/2008 6:19:02 AM|Einstein@Home|Started upload of h1_0923.55_S5R3__477_S5R3b_2_0
8/04/2008 6:19:02 AM|Einstein@Home|Started upload of h1_0923.55_S5R3__375_S5R3b_0_0
ID: 16522 · Report as offensive
ProfileJord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15632
Netherlands
Message 16523 - Posted: 8 Apr 2008, 9:53:08 UTC

Added as ticket [trac]#613[/trac].
ID: 16523 · Report as offensive
MarkJ
Volunteer tester
Help desk expert

Send message
Joined: 5 Mar 08
Posts: 272
Australia
Message 16525 - Posted: 8 Apr 2008, 11:15:58 UTC - in response to Message 16523.  

Added as ticket [trac]#613[/trac].


Thanks Jord
ID: 16525 · Report as offensive
John McLeod VII
Avatar

Send message
Joined: 29 Aug 05
Posts: 147
Message 16530 - Posted: 8 Apr 2008, 17:04:07 UTC

Not a whole lot that can be done about it though. There are numbers that cannot be represented exactly in binary. This is almost certainly pure rounding problems.

BOINC WIKI
ID: 16530 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5149
United Kingdom
Message 16532 - Posted: 8 Apr 2008, 18:45:25 UTC - in response to Message 16530.  

Not a whole lot that can be done about it though. There are numbers that cannot be represented exactly in binary. This is almost certainly pure rounding problems.

Store it in seconds, like every other BOINC time?
ID: 16532 · Report as offensive

Message boards : BOINC Manager : BOINC network/cpu times

Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.