Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 3
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well, I have done enough WU's to state the following, basing the information on the prietty graphics when the work unit is in progress
1) If on the graphs, the numbers change really fast (as in around 4-8 number changes per second), the work unit will be a longer one (16+ hrs)(usually, there were 4 hour circumstances in this one), the percentage doesn't change fast. (download ranges from 300000-600000 bytes) 2) If on the graphs, the numbers change not really fast (as in around .5-2 number changes per second) it is a short work unit (4-8 hrs)(usually is the case, although there have been long ones), the percentage jumps really quickly. (download ranges from 600000+ bytes) Is it just me, just my computer, or am I starting to see a vague trend going on? I just wanted to mention that... yep. ![]() ![]() |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
In my observations i've seen some work units complete in under 200 cycles. A unit was complete in 1 hour, advancing.. what .7% a cycle?
I've also seen work units use 20 hours of cpu time (from task list) but list over 117 hours from the GUI window of the UD program.. (I left it on while I was running a program along side it that used varying ammounts of CPU.) |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
One more thing I would like to add, my observations came from an AMD Athlon XP 3000+, and that it was just idle and only lprocessing with wcg rosetta.
![]() |
||
|
|
![]() |