| 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: 36
|
|
| Author |
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7846 Status: Offline Project Badges:
|
I just got 3 new beta tasks all on Windows. In the past the Windows beta tasks were short and the Linux ones were all in excess of 40 hours except for the ones which never got past 0.05%. This batch of beta tasks for Windows looks like the long variety with progress listed as 1.5% to 2.5% per hour. They are the BETA_BETA30_9800030_0812 type.
----------------------------------------Cheers Edit:spelling
Sgt. Joe
----------------------------------------*Minnesota Crunchers* [Edit 1 times, last edit by Sgt.Joe at Apr 30, 2025 2:48:26 AM] |
||
|
|
Grumpy Swede
Master Cruncher Svíþjóð Joined: Apr 10, 2020 Post Count: 2497 Status: Offline Project Badges:
|
iI have not received any Beta tasks at all, since 2025-04-26 0:25:17 UTC Those windows BETA_BETA30_9800029:xxxx tasks, were all long.
Two validated examples. The other two are still waiting for the wingman. https://www.worldcommunitygrid.org/contribution/workunit/706400661 https://www.worldcommunitygrid.org/contribution/workunit/706400355 |
||
|
|
tmedve
Senior Cruncher USA Joined: Nov 16, 2004 Post Count: 191 Status: Offline Project Badges:
|
Murphy struck me. Overnight the power went out. This morning, I restarted and the Beta tasks showed 100% and were ready to upload. They now show as errors and no credit granted. :(
----------------------------------------A lot of other MCM tasks got cancelled since they were now overdue because these Betas took so long. ![]() |
||
|
|
rilian
Veteran Cruncher Ukraine - we rule! Joined: Jun 17, 2007 Post Count: 1460 Status: Offline Project Badges:
|
I have a task 9800022 that is stuck on 51.71% after 10 minutes, and it is stuck in this % for 45 hours now
---------------------------------------- |
||
|
|
Boca Raton Community HS
Senior Cruncher Joined: Aug 27, 2021 Post Count: 209 Status: Offline Project Badges:
|
Murphy struck me. Overnight the power went out. This morning, I restarted and the Beta tasks showed 100% and were ready to upload. They now show as errors and no credit granted. :( A lot of other MCM tasks got cancelled since they were now overdue because these Betas took so long. Sorry about that- unfortunate bit of luck! I have a task 9800022 that is stuck on 51.71% after 10 minutes, and it is stuck in this % for 45 hours now I have not seen any 9800022 work units come through our systems. That might be the typical behavior but based on what we have seen they seem to stick at 0.5% (and stay there), move really slowly to 100% (days), or move relatively quickly to 100% (a few hours). We have some BETA30_9800023 still in progress and then finishing up all of the BETA30_9800030 within the next few minutes. It "looks" like they are waiting for everything </= BETA30_9800030 to return before anything new comes though? Interested to see what happens when the new deadline passes. |
||
|
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1326 Status: Offline Project Badges:
|
TPCBF wrote
----------------------------------------I am out of the office for a while now Thanks for sharing. Hopefully everything was successful :-) ![]() |
||
|
|
Boca Raton Community HS
Senior Cruncher Joined: Aug 27, 2021 Post Count: 209 Status: Offline Project Badges:
|
We have a series of 9800010 tasks that look to be almost impossible to process. They are progressing at 0.36%/hour on a dual xeon system (not terribly fast, but we paused all other work so definitely not a slow system). We went through and looked- only TWO of them have a wingman that created a result (pending validation). All of the others are still being processed by the wingman or aborted. So, if any of you have these... good luck!
Barely moving: BETA_BETA30_9800010_0879_1 BETA_BETA30_9800010_0880_1 BETA_BETA30_9800010_0881_1 BETA_BETA30_9800010_0882_1 BETA_BETA30_9800010_0899_1 BETA_BETA30_9800010_0900_1 BETA_BETA30_9800010_0903_1 BETA_BETA30_9800010_0926_0 BETA_BETA30_9800010_0928_0 BETA_BETA30_9800010_0942_0 BETA_BETA30_9800010_0943_0 BETA_BETA30_9800010_0944_0 BETA_BETA30_9800010_0950_1 BETA_BETA30_9800010_0952_0 BETA_BETA30_9800010_0953_1 BETA_BETA30_9800010_0955_0 BETA_BETA30_9800010_0957_0 BETA_BETA30_9800010_0958_0 BETA_BETA30_9800010_0959_0 BETA_BETA30_9800010_0960_0 BETA_BETA30_9800010_0962_0 BETA_BETA30_9800010_0963_0 |
||
|
|
Boca Raton Community HS
Senior Cruncher Joined: Aug 27, 2021 Post Count: 209 Status: Offline Project Badges:
|
The aforementioned tasks are actually finishing after nearly 11 days of processing (that made ARP1 tasks look easy). Some of their due dates were extended so most will be on time.
A few out of memory errors along the way, like other users. Is this a memory limitation set in BOINC or an error in the task its self that is requesting an unrealistically large amount of RAM? We are seeing a few resends but all is silent when it comes to new beta work. |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7846 Status: Offline Project Badges:
|
A few out of memory errors along the way, like other users. Is this a memory limitation set in BOINC or an error in the task its self that is requesting an unrealistically large amount of RAM? I believe it is the task itself which is requesting an inordinate amount of memory. My first thought is the task gets into a loop requesting memory and eventually will run until it exhausts all available memory. But it may be something different, such as the information it is working on has not been properly sized. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
lin lin
Cruncher China Joined: Feb 20, 2021 Post Count: 3 Status: Offline Project Badges:
|
BETA30_9800013_XXX also stucks at 0.5%.
|
||
|
|
|