We are (finally!) continuously generating FGRP3 WUs after making preliminary final adjustments to the "flops estimation". Current data indicates that (on average) the FGRP3 tasks take about 75% of the time the previous FGRP2 tasks took.
OPenCL Apps still have occasional trouble allocating (continuous) memory. While investigating this, GPU App versions have been turned off.
... Current data indicates that (on average) the FGRP3 tasks take about 75% of the time the previous FGRP2 tasks took.
I've seen a couple of completed tasks from a couple of my hosts and this seems about right to me. I don't have anything validated yet but I did a bit of digging into the tasks lists of wingmen until I found a validated quorum. The award was 80 credits.
From your figure quoted above, shouldn't the award be 660 credits?
Thanks for the application updates. I have both of my active hosts set to receive work for FGRP3 in addition to BRP5. Both applications are set to 0.33 GPU utilization factor.
I dunnow if it's THAT far out of whack, at least for the x86 app.
My old Thuban takes ~48K seconds to earn those 660 points. This is only a little more generous (~13%) than the recent S6 runs.
A lot of WUs of the latest set (LATeah0053C) come back with "validate errors" although the computation itself apparently went well. We are aware of this problem and investigating whether it is in the data, in the workunit setup or in validation. Until the problem is understood and fixed, we don't send out any more FGRP3 WUs.
Update: Fixed / adapted validator, sending out FGRP3 tasks again, "validate error" tasks will be looked at by the new validator and granted credit if appropriate.
We are (finally!)
)
We are (finally!) continuously generating FGRP3 WUs after making preliminary final adjustments to the "flops estimation". Current data indicates that (on average) the FGRP3 tasks take about 75% of the time the previous FGRP2 tasks took.
OPenCL Apps still have occasional trouble allocating (continuous) memory. While investigating this, GPU App versions have been turned off.
BM
BM
Got one about 10 minutes
)
Got one about 10 minutes ago..it came with about 61 minutes, 59 min. to go..
Don't see my Wingman yet :) :) :) :)
RE: ... Current data
)
I've seen a couple of completed tasks from a couple of my hosts and this seems about right to me. I don't have anything validated yet but I did a bit of digging into the tasks lists of wingmen until I found a validated quorum. The award was 80 credits.
From your figure quoted above, shouldn't the award be 660 credits?
Cheers,
Gary.
RE: From your figure quoted
)
Thanks, fixed for newly generated and for not yet validated WUs.
I can't do anything about the WUs that were already validated, though.
BM
BM
660 is too high and 80 is too
)
660 is too high and 80 is too low.
My task will be done soon for a total of 24 hr.44 minues. This about the same as my Grav. Wave SSE2 tasks and for which I get appr. 390 credits.
The same number of credits would be fair for the FGRP3 tasks - 390.83. My task will be completed in 44 minutes or so...
LATeah0052C_32.0_1040_-8.67e-10_1
Thanks for the application
)
Thanks for the application updates. I have both of my active hosts set to receive work for FGRP3 in addition to BRP5. Both applications are set to 0.33 GPU utilization factor.
You were right (as usual). I
)
You were right (as usual). I got 660 for the FGRP3.
Seems like too much for a short piece like that...
Thanks....
I dunnow if it's THAT far out
)
I dunnow if it's THAT far out of whack, at least for the x86 app.
My old Thuban takes ~48K seconds to earn those 660 points. This is only a little more generous (~13%) than the recent S6 runs.
A lot of WUs of the latest
)
A lot of WUs of the latest set (LATeah0053C) come back with "validate errors" although the computation itself apparently went well. We are aware of this problem and investigating whether it is in the data, in the workunit setup or in validation. Until the problem is understood and fixed, we don't send out any more FGRP3 WUs.
BM
BM
Update: Fixed / adapted
)
Update: Fixed / adapted validator, sending out FGRP3 tasks again, "validate error" tasks will be looked at by the new validator and granted credit if appropriate.
BM
BM