Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Member(s) browsing this thread: xensazn , TonyEllis |
Thread Status: Active Total posts in this thread: 3280
|
![]() |
Author |
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12408 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
It seems to me from what has been said that these units need a longer deadline if that can be done, even if they need to be called something else like ARP2. I am sure that the 24/7 crunchers would not mind. Their main gripe would be if they were timed out.
Presumably it would mean much longer intervals between checkpoints? There has been a lot of talk in the past about the short 7-day deadline and the current length of checkpoint interval for anyone not crunching 24/7 or with automated system updates. No problem here as I am still on Win7. Calling them ARP2 would enable those machines to be opted out. Do I assume correctly that the 3 test units were the 3 stuck in 084, one of which I had identified yesterday as moving on after being stuck for 6 weeks? Mike |
||
|
BladeD
Ace Cruncher USA Joined: Nov 17, 2004 Post Count: 28976 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Africa Rainfall Project 7.32
----------------------------------------Name ARP1_0020499_112 State Aborted by project |
||
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12408 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
BladeD
The usual reason for project abortion is if it was a resend because of non-return which was then returned late but before you had reached a checkpoint. Having not reached any checkpoint they would assume that you hadn't started it and therefore aborted it to prevent a waste of resources. If this is not the circumstance then please give a bit more information. Mike |
||
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12408 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Mini update!
The leading ultra is now 12 generations behind the last of the stuck units. One of the stuck units in generation 084 has moved on to the next generation after being stuck for 6 weeks, but no movement yet on the other 2 advised. The leading generation and the leading accelerated (priority) generation had moved on 1 generation to 122 & 112 respectively and the leading extreme generation has now done so, so the definitions are back to -10 & -15. That could be because none of generation 107 had been created until the last 24 hours. There was a slight increase in the validations so the forecast is now 22 October 2022. Mike |
||
|
Unixchick
Veteran Cruncher Joined: Apr 16, 2020 Post Count: 977 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() |
could be nothing... but just in case there is an issue. There was a 20 minute delay in me getting a new WU when requested, when usually there is no delay. When I did get a WU it was a resend.
I post this in case someone else has an similar issue, but I hope it is nothing. |
||
|
geophi
Advanced Cruncher U.S. Joined: Sep 3, 2007 Post Count: 104 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I've had occasional delays in getting ARP tasks for the last 6-8 hours.
|
||
|
BladeD
Ace Cruncher USA Joined: Nov 17, 2004 Post Count: 28976 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I've had occasional delays in getting ARP tasks for the last 6-8 hours. Yep, I'm waiting for some now. |
||
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12408 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
WCG turns them around as soon as they come back in. It takes about 15 minutes to create the next generation. As there are only 35,609 units, there are only 71,218 jobs for them to send out which means that they are spread thinly.
Those who hold more than 1 or 2 spare are holding up the supply to others and themselves. They are readily available but not necessarily immediately. Mike |
||
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12408 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Mini update!
The leading ultra is now 11 generations behind the last of the stuck units. One of the stuck units in generation 084 has moved on to the next generation after being stuck for 6 weeks, but no movement yet on the other 2 advised. The 1 hasn't moved for days. Are they stuck again? The leading generation and the leading accelerated (priority) generation had moved on 2 generation to 123 & 113 respectively and the leading extreme generation has now done so, so the definitions are back to -10 & -15. There was a slight increase in the validations so the forecast is now 18 October 2022. Mike |
||
|
|
![]() |