New work units completing in 38 seconds
Message boards : Number crunching : New work units completing in 38 seconds
| Author | Message | |
|---|---|---|
|
Am I the only one whose work units are completing so quickly. It takes about 24 seconds to complete 1%. Then about 26 seconds to complete 3%. Then the rate goes exponential to 100% in 38 seconds. I am going through a large number of work units. I have a quad core processor and on three of the cores I have older work units that are going to take about three hours to complete. It is just the most recent work units that are completing so fast. |
||
ID:
5977 | Rating: 0
| rate:
/
|
||
|
Am I the only one whose work units are completing so quickly. It takes about 24 seconds to complete 1%. Then about 26 seconds to complete 3%. Then the rate goes exponential to 100% in 38 seconds. I am going through a large number of work units. I have a quad core processor and on three of the cores I have older work units that are going to take about three hours to complete. It is just the most recent work units that are completing so fast. Apparently most people are having this happen as they went through all their available workunits in record time. Got a feeling this isn't right but will have to wait till the Docking people notice it. My 3.4GHz quad core usually finishes a workunit in about 2.5 hours. So since these are taking less than a minute these must be an error or something special they are testing. They do seem to be validating and giving the default credit though. Any Docking project administrators out there that know what's happening? |
||
|
ID:
5978 | Rating: 0
| rate:
/
|
||
|
Am I the only one whose work units are completing so quickly. It takes about 24 seconds to complete 1%. Then about 26 seconds to complete 3%. Then the rate goes exponential to 100% in 38 seconds. I am going through a large number of work units. I have a quad core processor and on three of the cores I have older work units that are going to take about three hours to complete. It is just the most recent work units that are completing so fast. You are right about the getting credit. I am getting 102 credits for every work unit completed! So in 12 hours I'll get more than 115,000 credits. I don't know if I get that many work units or not, but I have been getting them for the last hour no problem. |
||
|
ID:
5979 | Rating: 0
| rate:
/
|
||
|
I have same "problem". WU completed in 1 minute and 102 credites granted.
|
||
|
ID:
5980 | Rating: 0
| rate:
/
|
||
|
Well, I'm just not getting work at all. |
||
|
ID:
5981 | Rating: 0
| rate:
/
|
||
|
You've all got so slow machines,
mine only took 27 seconds
Well, I'm just not getting work at all. Me not as well, perhaps the actual bunch was ready too fast. Or someone saw the problem and stopped the sending. ____________ Gruesse vom Saenger For questions about Boinc look in the BOINC-Wiki |
||
|
ID:
5982 | Rating: 0
| rate:
/
|
||
|
I think the reason that little work is now available is because we all burned through those 40,000+ workunits in under a minute each and so they've mostly all been vlaidated now. I too am now only getting a few a day (probably someone's aborted units).
|
||
|
ID:
5984 | Rating: 0
| rate:
/
|
||
|
Well, I'm just not getting work at all. Hi, the reason of not getting tasks is that docking was not generating enough workunits so there was a "starvation". But now the problem should be solved. Can you please check to see if it is normal now? Thanks a lot! |
||
|
ID:
5988 | Rating: 0
| rate:
/
|
||
|
I think the reason that little work is now available is because we all burned through those 40,000+ workunits in under a minute each and so they've mostly all been vlaidated now. I too am now only getting a few a day (probably someone's aborted units). Hi, we are investigating the problem, there are some work going on in the server room, we don't know for sure whether it is related to that. We will keep you posted. Please let us know if the short time tasks observed again, thank you very much! |
||
|
ID:
5989 | Rating: 0
| rate:
/
|
||
|
Miracle ! I just have a small 2.8GHz Pentium 4 Core Duo, and in the last 24 hours my credit burst out with a huge number of tasks completing in only 1'45" when it usually requires around 9 hours. Now it has turned back to more realistic performances. |
||
|
ID:
5990 | Rating: 0
| rate:
/
|
||
|
Looks like Docking is back to producing what is for my PCs a normal duration WU of about 2.5 hours again. And it looks like its got some WUs available again.
|
||
|
ID:
5991 | Rating: 0
| rate:
/
|
||
|
Looks like Docking is back to producing what is for my PCs a normal duration WU of about 2.5 hours again. And it looks like its got some WUs available again. Thank you for letting us know! Please let us know if the problem observed again. |
||
|
ID:
5992 | Rating: 0
| rate:
/
|
||
|
Everything seems OK now. Thanks to Docking Team. |
||
|
ID:
5993 | Rating: 0
| rate:
/
|
||
|
Yes, Thanks Docking Team for getting everything fixed and running smoothly again.
|
||
|
ID:
5994 | Rating: 0
| rate:
/
|
||
|
I'm still not getting workunits on any of my machines and some have already run dry. I hit update and it does check but then says "0 workunits sent." |
||
|
ID:
5995 | Rating: 0
| rate:
/
|
||
|
I'm still not getting workunits on any of my machines and some have already run dry. I hit update and it does check but then says "0 workunits sent." errr, "Scheduler request completed, got 0 new tasks." |
||
|
ID:
5996 | Rating: 0
| rate:
/
|
||
|
I'm still not getting workunits on any of my machines and some have already run dry. I hit update and it does check but then says "0 workunits sent." How about now? Still getting the 0 new tasks error? Thanks! |
||
|
ID:
5997 | Rating: 0
| rate:
/
|
||
|
I get WU, but again they are completed in 1 minute, |
||
|
ID:
5998 | Rating: 0
| rate:
/
|
||
|
I get WU, but again they are completed in 1 minute, Hi, we noticed that the workunits '1ajx1dif' are the ones that complete within 1 minutes, can you please abort the tasks that run '1ajx1dif', and see if other workunits take longer? Thank you very much! |
||
|
ID:
5999 | Rating: 0
| rate:
/
|
||
|
Now I have 1d4h1diff and they take more than 3 hours. For now it is OK. |
||
|
ID:
6000 | Rating: 0
| rate:
/
|
||
|
Now I have 1d4h1diff and they take more than 3 hours. For now it is OK. Thanks for the update! |
||
|
ID:
6001 | Rating: 0
| rate:
/
|
||
|
Hi.
|
||
|
ID:
6008 | Rating: 0
| rate:
/
|
||
|
Hi. Looked at my host's doing Docking, but only seeing 'normal runtimes' of about ~3 hours to 3:30 hours. All 1d4idif_mod14crossdockinghiv_1xxx_yyyyyy_0 , found 1 with 2:20 hours, but none with only ~40 minutes, to complete. SETI@home sometimes has ' Ghost's WU's' or empty WU's through heavy RADAR Blanking, they take a few seconds to 'complete'. ____________ 
Knight who says N! Ni Ni |
||
|
ID:
6009 | Rating: 0
| rate:
/
|
||
|
Hi.
|
||
|
ID:
6010 | Rating: 0
| rate:
/
|
||
|
In addition to the short run times, I'm getting a lot of Compute Error WUs. |
||
|
ID:
6011 | Rating: 0
| rate:
/
|
||
|
Hi.
|
||
|
ID:
6012 | Rating: 0
| rate:
/
|
||
|
I had a heap of wu's that either had very short run times or errored out last night. They were all on my Linux box and all from the 1hsg1dif series. |
||
|
ID:
6016 | Rating: 0
| rate:
/
|
||
Message boards : Number crunching : New work units completing in 38 seconds
Database Error: The MySQL server is running with the --read-only option so it cannot execute this statement
array(3) {
[0]=>
array(7) {
["file"]=>
string(47) "/boinc/projects/docking/html_v2/inc/db_conn.inc"
["line"]=>
int(97)
["function"]=>
string(8) "do_query"
["class"]=>
string(6) "DbConn"
["object"]=>
object(DbConn)#32 (2) {
["db_conn"]=>
resource(126) of type (mysql link persistent)
["db_name"]=>
string(7) "docking"
}
["type"]=>
string(2) "->"
["args"]=>
array(1) {
[0]=>
&string(51) "update DBNAME.thread set views=views+1 where id=553"
}
}
[1]=>
array(7) {
["file"]=>
string(48) "/boinc/projects/docking/html_v2/inc/forum_db.inc"
["line"]=>
int(60)
["function"]=>
string(6) "update"
["class"]=>
string(6) "DbConn"
["object"]=>
object(DbConn)#32 (2) {
["db_conn"]=>
resource(126) of type (mysql link persistent)
["db_name"]=>
string(7) "docking"
}
["type"]=>
string(2) "->"
["args"]=>
array(3) {
[0]=>
object(BoincThread)#3 (16) {
["id"]=>
string(3) "553"
["forum"]=>
string(1) "2"
["owner"]=>
string(3) "333"
["status"]=>
string(1) "0"
["title"]=>
string(39) "New work units completing in 38 seconds"
["timestamp"]=>
string(10) "1283631891"
["views"]=>
string(3) "683"
["replies"]=>
string(2) "26"
["activity"]=>
string(19) "3.5863647252207e-68"
["sufferers"]=>
string(1) "0"
["score"]=>
string(1) "0"
["votes"]=>
string(1) "0"
["create_time"]=>
string(10) "1282179062"
["hidden"]=>
string(1) "0"
["sticky"]=>
string(1) "0"
["locked"]=>
string(1) "0"
}
[1]=>
&string(6) "thread"
[2]=>
&string(13) "views=views+1"
}
}
[2]=>
array(7) {
["file"]=>
string(63) "/boinc/projects/docking/html_v2/user/community/forum/thread.php"
["line"]=>
int(184)
["function"]=>
string(6) "update"
["class"]=>
string(11) "BoincThread"
["object"]=>
object(BoincThread)#3 (16) {
["id"]=>
string(3) "553"
["forum"]=>
string(1) "2"
["owner"]=>
string(3) "333"
["status"]=>
string(1) "0"
["title"]=>
string(39) "New work units completing in 38 seconds"
["timestamp"]=>
string(10) "1283631891"
["views"]=>
string(3) "683"
["replies"]=>
string(2) "26"
["activity"]=>
string(19) "3.5863647252207e-68"
["sufferers"]=>
string(1) "0"
["score"]=>
string(1) "0"
["votes"]=>
string(1) "0"
["create_time"]=>
string(10) "1282179062"
["hidden"]=>
string(1) "0"
["sticky"]=>
string(1) "0"
["locked"]=>
string(1) "0"
}
["type"]=>
string(2) "->"
["args"]=>
array(1) {
[0]=>
&string(13) "views=views+1"
}
}
}
query: update docking.thread set views=views+1 where id=553