New Beta Test starting Oct 31, 2013

[D_A]

We will be conducting a new beta test starting today. This test will have system requirements of:

400MB Ram
512MB of disk space
10MB result files

The initial beta test will have 5000 work units, with a quorum of 2. This means that 10,000 results will be sent out. I will be sending them out slowly so they could take a few hours to distribute. This test will be for Windows, Mac and Linux. Android will not be included in this beta test.

Thanks,
-Uplinger

No word yet on 32 or 64bit, though I doubt 64bit linux will be in this first beta test.

Edit: 32 and 64bit on Windows and Linux, 64bit only on Mac.

[Evantaur]

got a few

[anubis]

None for me

[D_A]

I just got the one. Might be a longer second stage beta, or it might go into production soon. We'll find out in due time I suppose.

[Evantaur]

World Community Grid	7.19 Beta Test	BETA_BETA_9999985_0263_0	00:00:59 (00:00:57)	98,05	0,500	07:21:24	10.11.2013 8:28:36		Running	hellhound	
World Community Grid	7.19 Beta Test	BETA_BETA_9999988_0117_0	00:00:59 (00:00:57)	97,55	0,500	07:21:24	10.11.2013 9:28:30		Running	hellhound

7 hours 21 minutes

[PoppaGeek]

got 2 64 bit linux, est. run time 10:31 Opteron 8356 @ 2.3

Kinda big for HCC?

[PoppaGeek]

For those not following the thread at WCG the BETAS have a "quirk"

First Beta WU finished after 1 hour 55 minutes.

The WU having 0.500% progress after 45 minutes and then jumped to 20.000% 10 minutes later, jumped to 40.000%. So it seems to be no bug - just let those WUs crunch undisturbed.
Edit: Another jump to 60.000% just happened.

Do not worry if they seem stuck.

EDIT:
I have one "stuck" and 2 progressing normally(I got another one).

[PoppaGeek]

Link

First thanks to all of the Beta testers. This new application has a larger number of different types of workunits than normal. This results in several possible paths through the code and some variance in workunit completion time and time between checkpoints.

The issue with workunits being stuck at 0.5% is an issue with the percent complete calculation. If the application is using cpu time it is probably not stuck so please let it continue to run for a while to verify. The 0.5% is some initialization which is taking longer for some of the types of workunits. We will correct this and determine a better way to show progress during the initialization.

The application should checkpoint at most every ten minutes. This is because some of the types of workunits produce larger checkpoint files and this will help limit disk I/O. Every workunit should checkpoint so we are looking into the ones that are not checkpointing.

The large output file errors are an issue with this being new research. We anticipated a smaller percentage of these so I apologize there are more than anticipated. The applicaitoin includes input parameters to limit the output sent back to the most critical and these parameters will be enhanced as we go. The next beta should have a very minimal amount of these. All users are getting credit for these errors.

Thanks again for all the help in getting new research running.

Thanks,
armstrdj

[Evantaur]

Task                Host                CPUtime        Rtime           points     PPH | PPD
-----------------------------------------------------------------------------------------------
BETA            hellhound               1.71            1.71            38.3    22.39 | 537.36
Average runtime per task: 1.71 h        Average Points per hour: 22.39

looks like not worth it :P

[PoppaGeek]

2 finished a little over 5 hours each.

third went 6:30 hours

[Rob_B]

I have a few validated that were done in 2-3 hours and one in just 10 minutes. But also had 3 errors already.
Funny thing is that I'm my own wingman on one of the wu's that errored

[Evantaur]

got 4 of them stuck :P

[D_A]

Mine died. Oh well ... problems are being found which means they get fixed and we get more beta units!

[[XC] Oj101]

Not one here

[OldChap]

16 + a re-send here but on the smaller rigs nothing for the 2 32's

Huge disparity in times projected and in running for some wu's

The re-send errored 131 for the primary user so I expect the same on that one but I only brought mine to the top a few hours ago and am waiting on the first completion.

Had one wu that sat at 0.5% for 2h30m then it jumped to 50% (where it has stayed since)

Getting 99% plus efficiency with these



an hour later:

[jeanguy2]

Only got one FAAH beta 7.19 (beta_beta_9999987_0336_0) WU on a 2600K WIN 7 cruncher. It ran for 03:56:30 but then produced an upload error on completion.

Details below:

Run complete, CPU time: 13919.860029
11:48:26 (23596): called boinc_finish

</stderr_txt>
<message>
upload failure: <file_xfer_error>
<file_name>BETA_BETA_9999987_0336_0_0</file_name>
<error_code>-131</error_code>
</file_xfer_error>

[0ne.shot]

I haven't seen a beta WU on my rigs yet.

[OldChap]

Only 10,000 in the first tranch and quite a few problems to fix so I am sure that there will be quite a few more

Patience you must have

(and betas turned on in preferences)

[NKrader]

still have none...

[yojimbo197]

still have none...

Me neither. I'm beginning to wonder if its discrimination against Linux.....

[OldChap]

Batch 1 were issued in the first hour and a half with re-sends spread over about 24 hours..... Be lucky for batch 2 when they test their fixes

[D_A]

Me neither. I'm beginning to wonder if its discrimination against Linux.....

Nope, just a very limited number of units all round. 10,000 total from memory. I got one. I would have liked a queue full, but that just ain't gonna happen.

[Evantaur]

looks like they ran out of FAHH tasks too

[OldChap]

I can't tell because I am working through a whole batch of work that is more difficult, runs longer, gives less points and is generally a PITA. When this happens then the rigs go into High priority mode and don't fetch new work (not needed due to longer run times). WCG work schedulers are up though.

[nanoprobe]

The 10,000 original tasks were gone jn 1.5 hours. The beta started around midnight EST so many of us missed them. I got 21 resends, they all failed but I still got credit so not all was in vain.