Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Beta Testing Forum: Beta Test Support Forum Thread: New Set of Beta WU's - FAAH |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 484
|
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Bah! Getting some server aborts. Wish I could get my clients to crunch beta work instead of regular work that is due five days later.
|
||
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2977 Status: Offline Project Badges: |
Questar, simple - just set the "Switch between applications every ..." to 7200 (instead of the standard 60). Then, this'll force WU's with a shorter than normal deadline to the top. It works wonders for me...
---------------------------------------- |
||
|
TimAndHedy
Senior Cruncher Joined: Jan 27, 2009 Post Count: 267 Status: Offline Project Badges: |
Did anyone else have troubles with these type beta units on Overclocked AMD chips?
BETA_ dg01_ a089_ pcb009_ 1-- I had a Invalid on one system and on my 1055T I had errors and it seemed to kill BOINC(WCG stopped running and the UI had no info in it. The messages and tasks tabs were empty). This happened 3 times. There appeared to be no problems on the Intel systems. Coincidence? These systems have been solid for months and now that the betas are gone everything seems to be back to normal. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
No trouble here, but did see one dg01 [DDDT2] aborted by server. Had not realized that this Beta was circulated with extra copy and mine just sat at end of a 1 days queue. The quicker 2 were valid, plus 1 I'd started manually.
--//-- PS: Now at 145 Days... 22 days advance on this New DL Server test :D Oh, on switch times to force these short deadline tasks ahead, 7000-7200 minutes is way over top. Subtract cache size from deadline and set value at that. 4500 minutes would be more than enough including the safety margins BOINC uses, to invoke/push high priority processing of repairs/betas. Just try it. :D |
||
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: |
Oh, on switch times to force these short deadline tasks ahead, 7000-7200 minutes is way over top. Subtract cache size from deadline and set value at that. 4500 minutes would be more than enough including the safety margins BOINC uses, to invoke/push high priority processing of repairs/betas. Just try it. :D Won't work if your cache is less than 7/8 (.875) day on 4 day deadlines. (I use .1 for betas) The simplest method I have found is to set 1440 for each day of deadline. ( 2880 for 2 day, 5760 for 4 day etc.) That will remove cache size from the equation.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
----------------------------------------[Edit 1 times, last edit by nanoprobe at Jul 15, 2011 12:00:51 PM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
That's why I said ''Subtract cache size from deadline" to equate your adapted value, but yes doing true KISS, 1440 for each day of deadline does not fail.
Any client which runs with a 0.1 cache, would get to those ''rush'' jobs in short order... unless there is rush rush. When running with 0.1 cache during a multi-science beta such as now, would miss out on the opportunity to get anything else. I picked up 4 DDDT2, then shortly after got 4 FAAH Beta repairs with a bigger [normal-ish] cache. They sprung ahead of course of the 4 day due Betas... which is fun to watch :D --//-- |
||
|
kateiacy
Veteran Cruncher USA Joined: Jan 23, 2010 Post Count: 1027 Status: Offline Project Badges: |
Did anyone else have troubles with these type beta units on Overclocked AMD chips? BETA_ dg01_ a089_ pcb009_ 1-- I had a Invalid on one system and on my 1055T I had errors and it seemed to kill BOINC(WCG stopped running and the UI had no info in it. The messages and tasks tabs were empty). This happened 3 times.. My AMD Phenom II X4 610e (not overclocked) had no problem with DDDT2 betas: BETA_ dg01_ a084_ pr67b0_ 1-- kate-amd64 Valid 7/13/11 22:50:44 7/14/11 09:47:52 3.30 89.9 / 73.0 BETA_ dg01_ a083_ pr34a1_ 0-- kate-amd64 Valid 7/13/11 22:48:34 7/14/11 02:36:05 3.61 98.6 / 105.9 BETA_ dg01_ a083_ pr45b1_ 0-- kate-amd64 Valid 7/13/11 22:48:34 7/14/11 02:36:05 3.68 100.5 / 89.8 BETA_ dg01_ a083_ pr56a1_ 0-- kate-amd64 Valid 7/13/11 22:48:34 7/14/11 02:36:05 3.61 98.5 / 83.6T2 |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Questar, simple - just set the "Switch between applications every ..." to 7200 (instead of the standard 60). Then, this'll force WU's with a shorter than normal deadline to the top. It works wonders for me... Cool, thanks, I'll give this a try. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yes, thanks for keeping us informed Our next project is actually pretty modest in terms of bandwidth requirements. More info about that in the future. Doesn't sound like it's re-launch of DDDT1/CEP1 But by following past revealed goals, that would entail 2 beta's... one for 32 bits and one for 64 bits, if done consecutive and not concurrent :P Per noon update in need of 35 days towards ruby |
||
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: |
Any client which runs with a 0.1 cache, would get to those ''rush'' jobs in short order... unless there is rush rush. When running with 0.1 cache during a multi-science beta such as now, would miss out on the opportunity to get anything else. I picked up 4 DDDT2, then shortly after got 4 FAAH Beta repairs with a bigger [normal-ish] cache. They sprung ahead of course of the 4 day due Betas... which is fun to watch :D When it's 1 or 2 betas per core does cache size even matter? I've tried different sizes. It didn't seem to make any difference.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
|