Participants with excessive work units and excessive No Reply


log in

Advanced search

Questions and Answers : Wish list : Participants with excessive work units and excessive No Reply

Author Message
Profile Rustys Toy
Send message
Joined: 5 Mar 07
Posts: 4
Credit: 188,835
RAC: 0
United States
Message 701160 - Posted: 18 Jan 2008, 18:10:44 UTC

I have had several WU i completed in Nov time frame which are still pending granted credit. I checked the other participant on one and they had over 1400 WU in progress. There average turn around was 55 days.
This is not an isolated case although it seems there was a spike for Nov downloads. A single cpu computer doesn't need 1400+ WU in its queue.

I think the download rules need to be reviewed.

Profile Earl M. Kitts
Send message
Joined: 15 May 99
Posts: 2
Credit: 154,294
RAC: 0
United States
Message 703566 - Posted: 24 Jan 2008, 14:11:49 UTC - in response to Message 701160.
Last modified: 24 Jan 2008, 14:14:57 UTC

I agree with you, found 1 had a 1 gig computer and has 100 work units to process, turn around time is 8 days.
____________

Profile BilBg
Volunteer tester
Avatar
Send message
Joined: 27 May 07
Posts: 2570
Credit: 5,876,851
RAC: 2,712
Bulgaria
Message 719715 - Posted: 29 Feb 2008, 3:23:55 UTC - in response to Message 703566.



I agree with you, found 1 had a 1 gig computer and has 100 work units to process, turn around time is 8 days.



Turn around time of 8 days doesn't mean that this computer produces 1 result per 8 days.

BOINC is like conveyor - it gets WorkUnits from one side and gives results to the other.

Turn around time of 8 days means that WU entered the queue 8 days before it has been processed
(i.e. computed, produced result, result uploaded & reported)

Meanwhile (while this WU has been waiting in the queue) the computer ended and
reported many more WU/results (10...100)

Your computer "AMD Athlon(tm) 64 X2 Dual Core Processor 3800+" has
"Average turnaround time 2.82 days"
but I'm sure that it computes a WU every 2-4 hours.


****************************************

---> Suggestion to Web pages developer:

Add "Average number of results computed/uploaded/reported per day"

because many people confuse that to be equivalent to
"Average turnaround time"

****************************************


Profile BilBg
Volunteer tester
Avatar
Send message
Joined: 27 May 07
Posts: 2570
Credit: 5,876,851
RAC: 2,712
Bulgaria
Message 724092 - Posted: 10 Mar 2008, 9:13:42 UTC
Last modified: 10 Mar 2008, 9:16:02 UTC

.

Turn around time depends mostly on the size of the WU cache -
the more WorkUnits on your computer - the bigger turn around time.

Size of the WU cache depends on your preferences -
"Maintain enough work for an additional [XX] days".

.

John McLeod VII
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 15 Jul 99
Posts: 24098
Credit: 517,932
RAC: 146
United States
Message 724128 - Posted: 10 Mar 2008, 10:44:21 UTC

Turn around time depends on several factors, among them:

Size of the cache.
Number of projects attached and the resource shares allocated.
The amount of time the computer spends on.
____________


BOINC WIKI

Profile BilBg
Volunteer tester
Avatar
Send message
Joined: 27 May 07
Posts: 2570
Credit: 5,876,851
RAC: 2,712
Bulgaria
Message 724139 - Posted: 10 Mar 2008, 11:02:20 UTC - in response to Message 724128.
Last modified: 10 Mar 2008, 11:50:54 UTC


Turn around time depends on several factors, among them:

Size of the cache.
Number of projects attached and the resource shares allocated.
The amount of time the computer spends on.




It has to be noted clearly that "Turn around time" has NO
direct corelation with RAC.

"Size of the cache" has impact on the "Turn around time"
but NOT on the RAC

"Number of projects attached and the resource shares allocated.
The amount of time the computer spends on"
HAVE impact on the RAC.


You can have big ("slow") "Turn around time" AND have good RAC
if your computer:
- is fast (whatever that means)
- works all the time (BOINC is allowed to run 100% of the time using 100% CPU)
- is almost idle all of the time (not running "heavy" apps - i.e. you use it mainly for textprocessing, web browsing, play Solitaire :), etc... )
(some (3D "fancy") screen savers ARE in fact "heavy" apps - if you use them they "eat" CPU time and very often they continue to run after the monitor is asleep and you can't see them)
- you don't "sleep" the computer, only the monitor ("sleeping" computer is of course not working (but the LEDs and (maybe) fans :) ))

.

John McLeod VII
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 15 Jul 99
Posts: 24098
Credit: 517,932
RAC: 146
United States
Message 724270 - Posted: 10 Mar 2008, 20:02:48 UTC - in response to Message 724139.


Turn around time depends on several factors, among them:

Size of the cache.
Number of projects attached and the resource shares allocated.
The amount of time the computer spends on.




It has to be noted clearly that "Turn around time" has NO
direct corelation with RAC.

"Size of the cache" has impact on the "Turn around time"
but NOT on the RAC

"Number of projects attached and the resource shares allocated.
The amount of time the computer spends on"
HAVE impact on the RAC.


You can have big ("slow") "Turn around time" AND have good RAC
if your computer:
- is fast (whatever that means)
- works all the time (BOINC is allowed to run 100% of the time using 100% CPU)
- is almost idle all of the time (not running "heavy" apps - i.e. you use it mainly for textprocessing, web browsing, play Solitaire :), etc... )
(some (3D "fancy") screen savers ARE in fact "heavy" apps - if you use them they "eat" CPU time and very often they continue to run after the monitor is asleep and you can't see them)
- you don't "sleep" the computer, only the monitor ("sleeping" computer is of course not working (but the LEDs and (maybe) fans :) ))

.

Yes, The number of projects attached and the amount of time that the computer spends on have a correlation with RAC. They also have a correlation with turn around time.

Example: The user has a cache of 0.1 days, and takes 3 hours to complete a task. If the computer is only on for 2 hours a week, the computer is going to have a turn around time of about a week. If the only thing you change is the time spent on to 24 / 7, the computer is going to have a turn around time of around 5.4 hours (3 hours compute time + 0.1 hours waiting in the queue).

I have several computers attached to over 50 projects. Most tasks are completed just prior to the computation deadline, and returned not long before the report deadline. This makes the turn around time just about the same as the initial time to deadline.
____________


BOINC WIKI

Questions and Answers : Wish list : Participants with excessive work units and excessive No Reply

Copyright © 2014 University of California