NEW BATCH This time with 2 day reporting time
earliest start time for me was 2h33m ago
NEW BATCH This time with 2 day reporting time
earliest start time for me was 2h33m ago
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
I suppose my eight day queue has prevented me from getting any work units
Xtreme SUPERCOMPUTER
Nov 1 - Nov 8 Join Now!
Athlon64 3700+ KACAE 0605APAW @ 3455MHz 314x11 1.92v/Vapochill || Core 2 Duo E8500 Q807 @ 6060MHz 638x9.5 1.95v LN2 @ -120'c || Athlon64 FX-55 CABCE 0516WPMW @ 3916MHz 261x15 1.802v/LN2 @ -40c || DFI LP UT CFX3200-DR || DFI LP UT NF4 SLI-DR || DFI LP UT NF4 Ultra D || Sapphire X1950XT || 2x256MB Kingston HyperX BH-5 @ 290MHz 2-2-2-5 3.94v || 2x256MB G.Skill TCCD @ 350MHz 3-4-4-8 3.1v || 2x256MB Kingston HyperX BH-5 @ 294MHz 2-2-2-5 3.94vOriginally Posted by Jowy Atreides
Got 7, 5 Windows 2 Linux
I have 3 rigs running in high priority mode that received some... I think your rig just needs to be asking for work at the right timeI suppose my eight day queue has prevented me from getting any work units
I am still getting primary work in dribs and drabs ....have already had re-sends too
EDIT: Here's the reason my 4th rig got none so far:
spiders
119736 World Community Grid 04/11/2013 22:29:30 Sending scheduler request: To report completed tasks.
119737 World Community Grid 04/11/2013 22:29:30 Reporting 2 completed tasks
119738 World Community Grid 04/11/2013 22:29:30 Not requesting tasks: don't need
119739 World Community Grid 04/11/2013 22:29:33 Scheduler request completed
Last edited by OldChap; 11-04-2013 at 02:31 PM.
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
I got 14 beta wu's spread over 3 rigs. And all run in high priority.
But I'm running all rigs with a small cache. Just 1 day + 0.3 additional.
Mine are all running High Priority and the cache on all mine are less than 2 days.
Got 4 more Windows. So far 4 valid, 3 errors.
All but 3 of the betas I have gotten so far show no errors by me and wingman. All other have at least 1 error some several.
30 wu's
shortest 0.29hrs runtime
longest 12.59hrs runtime
average 3.77hrs runtime
valid 23
pv 7
errors 0 (so far)
max pphour (3700k) 29.7
min pphour (e5-26xx) 9.95
111 hours of runtime (4.5 days+) towards my gold beta badge
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
Got another new batch on the spiders rig this time.... it got missed yesterday
This is beta 7.22. you may also see re-sends from 7.21
Also, the new work units will end with "b_#" where # is some integer between 0 and 9.
Last edited by OldChap; 11-05-2013 at 02:00 PM.
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
Can you tell me the "Application" or "Name" as reported by BOINC? I have a MASSIVE queue (I messed up the settings) and I want to arrange either column by name and see if I was lucky enough to be sent some.
Xtreme SUPERCOMPUTER
Nov 1 - Nov 8 Join Now!
Athlon64 3700+ KACAE 0605APAW @ 3455MHz 314x11 1.92v/Vapochill || Core 2 Duo E8500 Q807 @ 6060MHz 638x9.5 1.95v LN2 @ -120'c || Athlon64 FX-55 CABCE 0516WPMW @ 3916MHz 261x15 1.802v/LN2 @ -40c || DFI LP UT CFX3200-DR || DFI LP UT NF4 SLI-DR || DFI LP UT NF4 Ultra D || Sapphire X1950XT || 2x256MB Kingston HyperX BH-5 @ 290MHz 2-2-2-5 3.94v || 2x256MB G.Skill TCCD @ 350MHz 3-4-4-8 3.1v || 2x256MB Kingston HyperX BH-5 @ 294MHz 2-2-2-5 3.94v
The Application is "Beta Test", and the unit names start with "BETA_BETA"
Last edited by D_A; 11-05-2013 at 02:11 PM.
[SIGPIC][/SIGPIC]
Had to extend my cache out a few days but I got four! W00T!
[SIGPIC][/SIGPIC]
I pushed mine to 4 days from 3 but the hard wu's I had over the last few days have put mine into high p already, still.... got 23 and 11 on the big rigs so far and still getting more for now. Sure helps to have wu's finishing close together and I aborted a couple of CEP's... just to make space of course
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
Got two
Name BETA_BETA_9999983_0519b_0
Application Beta Test 7.22
Workunit name BETA_BETA_9999983_0519b
State Running
Received 6.11.2013 0:29:33
Report deadline 8.11.2013 0:29:32
Estimated app speed 1,36 GFLOPs/sec
Estimated task size 71397 GFLOPs
CPU time at last checkpoint 00:00:00
CPU time 00:05:11
Elapsed time 00:05:14
Estimated time remaining 14:27:34
Name BETA_BETA_9999984_0318b_0
Application Beta Test 7.22
Workunit name BETA_BETA_9999984_0318b
State Running
Received 6.11.2013 1:00:39
Report deadline 8.11.2013 1:00:38
Estimated app speed 1,36 GFLOPs/sec
Estimated task size 71397 GFLOPs
CPU time at last checkpoint 00:00:00
CPU time 00:06:26
Elapsed time 00:06:31
Estimated time remaining 14:26:18
Member of XS WCG since 2006-11-25
A little something for you guys just before I head for bed...
You know how Dave says a picture paints a thousand words....I Managed a full loadout across both Spiders and Arachnid:
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
how the f? :O
I like large posteriors and I cannot prevaricate
The scheduler won't give you any more than it's certain you can complete by the VERY short deadline.
[SIGPIC][/SIGPIC]
wee!!
I like large posteriors and I cannot prevaricate
And I STILL haven't received ONE!
Xtreme SUPERCOMPUTER
Nov 1 - Nov 8 Join Now!
Athlon64 3700+ KACAE 0605APAW @ 3455MHz 314x11 1.92v/Vapochill || Core 2 Duo E8500 Q807 @ 6060MHz 638x9.5 1.95v LN2 @ -120'c || Athlon64 FX-55 CABCE 0516WPMW @ 3916MHz 261x15 1.802v/LN2 @ -40c || DFI LP UT CFX3200-DR || DFI LP UT NF4 SLI-DR || DFI LP UT NF4 Ultra D || Sapphire X1950XT || 2x256MB Kingston HyperX BH-5 @ 290MHz 2-2-2-5 3.94v || 2x256MB G.Skill TCCD @ 350MHz 3-4-4-8 3.1v || 2x256MB Kingston HyperX BH-5 @ 294MHz 2-2-2-5 3.94v
I just got 2 Beta Test 7.22 WUs!!!! It looks like someone is hogging them all!
All the v7.22 betas I got on Win7-x64 errored out. They start, run for about 10 sec, do an "exit(0)", restart, and repeat this until they hit a limit on the no of "exit(0)s" allowed (100).
My 1 machine that does not run w7-x64 runs XP-x64 and it ran the 1 short WU it got OK.
Think it's a bug in Win7-x64, surprise, surprise.
Don't know whether 32-bit XP vs W7 is similar.
Linux is reported as OK, Mac probably OK too.
----
Guys, before you go loading up on betas, please remember that WCG need and want diversity in hardware and OSes when they run beta tests.
In this case there are a number of different WU types too, so it won't hurt if you run a reasonable number of beta WUs under each of your hw/OS combos.
But doing things that detract from the results of the beta tests for the sake of a different-coloured little square on your WCG forum posts hardly fits in with why we are crunching for WCG.
But I do like the colour of my gold β badge
They have fixed numbers of units for each OS and variation because they're all coded slightly differently. Windows units don't run on Linux and v/v. WCG isn't like Test4Theory where the work units run in consistent virtual machines and the host OS isn't relevant, ours run on bare metal. It's not possible for one person with a huge farm of 64bit Linux machines to vacuum up all the units that could have gone to Windows or Mac.
[SIGPIC][/SIGPIC]
Seems they must have the Linux version sorted out as I see few errors. Windows is still buggered from the looks of it.
7.24 now as they are working through the issues
New Beta Test starting Nov 6, 2013 v7.24
This beta test is testing if we have fixed the issue with the too many exits issue.
This issue appears to have been caused by a change in the BOINC API layer for the research application. Every 10 seconds, the research application will check to see if the BOINC core client is still running. Previously, this check was done by iterating through all the running processes on the system to see if the process id could be found. This was changed to use the OpenProcess windows api call. The BOINC API treated any failure of this call as the core client not being there. However, beta test 7.23 confirmed that in the cases we were seeing it was returning "OpenProcess failed with error 5: Access is denied.". This represents a security policy issue rather than the core client not running. We suspect this has to do with the permission and user structure used when running BOINC as a service. We will pass this information along to BOINC for them to review and decide what to do.
In the meantime, we reverted this portion of the API back to the previous mechanism and have released this as version 7.24. We are hoping for a cleaner run this time.
My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!
Got 2 new Beta WUs (beta17_7.22) on a 3930k Win7 rig Both processed OK
Result Name Device Name Status Sent Time Time Due / Return Time CPU Time / Elapsed Time (hours) Claimed/ Granted BOINC Credit
BETA_ BETA_ 9999986_ 0819b_ 0-- ginette Valid 11/5/13 23:40:29 11/6/13 09:59:08 2.38 / 2.38 85.2 / 84.3
BETA_ BETA_ 9999986_ 0803b_ 0-- ginette Valid 11/5/13 23:40:29 11/6/13 09:59:08 0.48 / 0.48 17.3 / 19.5
Last edited by jeanguy2; 11-06-2013 at 09:00 AM.
Posting Permissions
Reply With Quote
Bookmarks