22hrs to go after 13hrs crunching

I wonder why all results with WUs aborted by server are removed from the database so quickly (i.e. they now disappeared from the results status page). Anyone knows?

There were some questions about work - I wanted to reiterate a different way what Keith said in the announcement:

Phase 2 has three types of workunits. A, B and C.

Each A workunit will generate 2 B workunits.
Each B workunit will generate 5000 C workunits.

Estimated runtime for an A workunit is 60 hours (give or take a lot of time)
Estimated runtime for a B workunit is 4-10 hours (give or take some time)
Estimated runtime for a C workunit is 2-5 hours (give or take some time)

Type A require LARGE memory (1.75MB) and have large result files. Thus they have the bandwidth limit set.
Type B and C require less memory (~750MB) and have large input files but reasonable result files.

So doing some quick estimates, for each workunit we will spend:

120 hours in type A (1 workunit * 2 results * 60 hours)
28 hours in type B (2 workunits * 2 results * 7 hours)
35,000 hours in type C (5000 workunits * 2 results * 3.5 hours)

The overwhelming time for this phase of project will be spent with type C workunits which will only have the 750MB ram limit on them.

Not sure what to make of this one.

One of my machines just finished up BETA_erag_a017_ps0005_2

Bonic shows it as 100% complete, no errors.

When it reached completion, bonic set it's status back to "Waiting To Run".
No Computation for task finished message, no upload of data.

Checking the results status here, it still shows it "In Progress" with the other 2 of 3 as "Valid".

I understand the quarum of 2 was met before mine finished, but did something perhaps happen on the server side to cause this one not to upload?

I saw some of my other beta's were canceled from the server side and understand how/why that was done. Did this one possibly fall thru the cracks somehow?

Edit: Resolved - When whatever happened with the WU, it went back to the "Waiting To Run" state and bonic continued to process the other tasks ahead of this one. I temporarily suspended all the tasks in between to possibly trigger this one to process again. It kept the completion at 100%, but apparently started back at the last checkpoint (80%). When it reached 120% it completed as one would normally expect.
Not sure what happened to automatically switch it to a waiting state like that when it finished, but it worked itself out.

Interim Report on Monster WU BETA_erag_a019_ps0000_2:

Machine running 24/7 and at 24 hours CPU Time to date, this WU shows 36.680% complete and running fine. Comparison of the CPU time and Calender time, indicates the WU is getting 97.9% of the CPU time. Based on completion rate to date, I estimate this WU, barring error, will complete in 65.5 hours from when it was started (10/6 15:06 hrs PDT).

Needless to say, I will not touch this machine until this WU has completed. One giant leap toward silver